DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to track token use in your own Anthropic or OpenAI app with Optimaizr

Wrap your existing API client in one line so optimAIzr can read your app's calls.

Who it is forA developer building an app on the Anthropic or OpenAI API who wants to see which calls spend the most tokens.

The problemAn API bill shows totals but not which calls re-send too much context or repeat work.

The outcomeYour app's API calls are wrapped so that the same optimAIzr report covers them alongside your other usage.

What you need first

  • Node.js 20.11 or later (22.13 or later to read opencode history)
  • Existing usage logs from Claude Code, Codex or opencode on this machine
  • A terminal

Steps

  1. Install the package with npm install optimaizr in your app's project. (inferred, check the README)
  2. Wrap your client with optimaizr.wrap(new Anthropic()) or optimaizr.wrap(new OpenAI()). (inferred, check the README)
  3. Run your app once so it makes its usual API calls.
  4. Run npx optimaizr to see where your tokens go.

Prompt for your agent

In the optimaizr repo, wrap the API client in <app path> with optimaizr.wrap, run the app once, then run `npx optimaizr` and report the Where it goes breakdown. Verify that the app still returns the same responses it returned before the wrap.

Caveat. The README does not say exactly what the wrapped client reports, so check the output after one run.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page