Supported agent
Your OpenCode usage, as a file in your repo.
tokenchit reads the OpenCode logs already on your machine and renders one embeddable card straight into your repository. The card is a file you commit, not a URL you depend on — nothing to rate-limit, nothing to go down.
$ npx -y @tokenchit/cli@latest generateFree and MIT. No account is needed to read your own numbers — publishing to the board is a separate, opt-in command.
What it reads
OpenCode records usage in a SQLite database rather than flat files. Reading it uses Node's built-in node:sqlite, which is why the CLI needs Node 22 or newer.
~/.local/share/opencode/opencode.dbNothing else is read, and nothing is sent. tokenchit sync and tokenchit recap make no network request at all; five tests in the repo fail on every push if that stops being true.
What it cannot tell you
Tokens are counted; some of the cost is not
OpenCode routes to whatever model you point it at, including self-hosted and bundled ones with no public per-token price. Those are counted in the token total and left out of the equivalent-cost figure, because inventing a rate for them would make the cost look complete when it is not. The card reports the share of tokens that are priced so you can see how much of the figure is covered.
Equivalent cost is not what you paid either. It is what these tokens would cost at list API rates, and most agent usage runs under a subscription where no per-token charge ever happens.
On the board, by opencode
Developers who chose to publish, ranked by opencode tokens over the last year. Figures are self-reported and bounded for plausibility, not audited.
| Rank | Developer | opencode tokens | Equiv. cost |
|---|---|---|---|
| 1 | @bucharitesh | 8.36B | $1,182 |
| 2 | @praveenMalagudi | 126M | $0 |
| 3 | @iyashjayesh | 17.6M | $0 |
| 4 | @NVJKKartik | 9.45M | $2 |
The other agents
One command covers all of them at once, and the card shows the mix.
- Claude Code
~/.claude*/projects/**/*.jsonl - Codex
~/.codex/sessions/**/rollout-*.jsonl - Gemini CLI
~/.gemini/tmp/*/chats/*.jsonl
Detected and deliberately unsupported: Copilot CLI records only a live context gauge, so there is no per-call token count to read.
Read your own numbers
One command. It finds your agents, shows your stats and writes the card. Publishing is a separate step you have to ask for.
$ npx -y @tokenchit/cli@latest generateOr tokenchit sync on its own to see the figures without writing anything. Source at github.com/iyashjayesh/tokenchit.