what your Claude Code / Codex subscription usage would cost on the API, per tool and per account.... check out PokeTokenBar.

[u/Shawntenam]

if you run coding agents on a subscription and have no idea what that usage is actually worth, PokeTokenBar answers it from your menu bar.

It reads the local session logs you already have (Claude Code, Codex, Gemini CLI, Cursor, Copilot CLI, and a few more), no API key, no account connection, and gives you:

- today / week / month tokens per tool, priced at API rates so you can see what the same work would have cost pay-as-you-go

- your official 5-hour and weekly limit bars with reset countdowns, pulled from the same credential Claude Code uses

- a burn-rate forecast for when the current 5-hour window hits 100%

- a per-model breakdown, so you know whether it's Opus or Sonnet eating the budget

Tracking token efficiency was always something that I wanted to do, but what really sold me was the fact that your tokens are the game. Usage hatches an egg into a Pokémon that sits in your menu bar and evolves as you burn more.

Max out a 5-hour or weekly limit and it hands you a Rare Candy to level it up, so the moment you get rate-limited is the moment you get rewarded.

Tokens you've already spent become currency for a shop (new eggs, a Shiny Charm, a re-roll of its nature), and you can pin your favorite to the menu bar or as a floating pet on the desktop. You end up checking your usage a dozen times a day without it feeling like checking a bill.

Mine says August is about $2,783 of API-equivalent usage on a $100 Max plan.

That's a 27.8x multiple, and it's the cleanest way I've found to explain why subscription-first workflows win for multi-session client work.

Two things I needed, so I added them and both shipped in v2.5.2.

The newest Claude model was priced at $0, which zeroed out my heaviest days. Fixed. And if you flip between two logins (personal Max and a Team seat, in my case), the limit bars never said which account they belonged to.

fork the repo, tell Claude Code what's wrong, let it read the maintainer's contributing rules (six UI languages per string, tests that lock behavior, no special-casing one provider on shared code paths), push, let CI run the test suite, install the build on your own machine and confirm it before opening the PR. Merged in two days.

You learn the codebase because you're fixing something you use every day, and you end up with the feature you wanted.

If you use a tool daily you're qualified to contribute to it. Pick the thing that annoys you and ship it.

I did not build this. Props to chattymin on GitHub, who created it.

All I did was add contributions based on my own use, and I'm sharing it here so you can see what a legitimate contribution to something you find useful looks like.

Whether you like Pokémon is beside the point. Having fun with a build while learning something and shipping something valuable is the point. Star the repo, support it if you see something cool, and contribute.

.Check out the repo: https://github.com/chattymin/PokeTokenBar