Install the plugins.
Two commands per tool. Nothing is compiled on your computer: each plugin ships or fetches a prebuilt, checksum-verified helper for your platform. The plugins send usage metadata only, never prompts, responses or code. Both plugins are open on GitHub: EDOS-Engineering/ork-meter-claude and EDOS-Engineering/ork-meter-codex.
Metering is free. Connecting a plugin and seeing your token usage in Ork Meter costs nothing. The plugins' optimizations (trimmed tool output, repeated-read and test-noise reduction, recoverable originals) run only while your account has Ork Meter Plus. Without Plus the plugin still meters and Claude Code or Codex runs exactly as before. Ork Meter never reports a savings figure it has not measured. See the plan page and Terms of Service.
Ork Meter for Claude Code
From a terminal, add the EDOS marketplace and install the plugin:
claude plugin marketplace add EDOS-Engineering/ork-meter-claude
claude plugin install ork-meter@edosThen run /ork-meter:connect once inside Claude Code. The plugin reads Claude Code's own token-counter metrics through a local receiver and sends the four token counters, a snapshot time, your self-declared plan, the plugin version and which Plus optimizations were active to Ork Meter. The plugin version and optimization labels are stored only if you opt in to measurement in your Plus preferences; otherwise Ork Meter drops them before anything is stored. Prompts, responses, tool content, session identifiers and account identifiers are discarded before delivery. With Plus, its hooks also reduce oversized tool output, repeated reads and test noise before they enter the model's context, keeping the full original on disk. The plugin carries prebuilt runtime binaries for macOS, Linux and Windows and verifies the one for your platform against its SHA-256 before running it.
Ork Meter for Codex
From a terminal, add the EDOS marketplace, install the plugin, then run its setup:
codex plugin marketplace add EDOS-Engineering/ork-meter-codex
codex plugin add ork-meter-codex@edos-codexSetup pairs your account in the browser, starts local capture of Codex's native telemetry and opens Codex with your existing model and permission settings; exit that session to stop capture and restore your configuration. What leaves your machine is allow-listed usage metadata: source, request ID, model, timestamp, token counts by category and any provider-reported charge. With Plus, a PostToolUse hook that you review once with /hooks reduces noisy shell output and keeps the exact original recoverable by handle. Nothing in your conversation is rewritten.
Where the helper comes from
The Codex plugin drives a small helper program, ork-meter, that does the pairing and capture. Setup downloads it for your platform from the ork-meter-codex GitHub Release matching the installed plugin version, verifies its SHA-256 against that release's manifest.json before writing anything, and installs it owner-only under your Codex profile's ork-meter-codex directory. A download whose digest does not match installs nothing. Releases are public, so the download needs no token. Each release is built by a reviewed workflow from a recorded ork-meter revision and carries build provenance attestations. The Claude Code plugin's runtime arrives inside the plugin itself the same way: prebuilt, with its digest file beside it.
Accounts
Ork Meter accounts are open to people in the United States aged 18 or older and sign in with GitHub; see the Terms of Service and Privacy Policy. Once connected, your dashboard's helper page shows whether each connection is authorised and how many usage events have been received; authorisation alone is not evidence of usage. Help is on the support page or from edos-labs@edos.io.