Puts Claude in your terminal to understand your codebase, edit files and handle git workflows.
Optimaizr
blendbunjaku · App
Optimaizr is a local command line tool that finds where tokens are spent in Claude Code and Codex sessions and in your own Anthropic or OpenAI API calls. It reads token counts from the logs already on your machine, shows spend by model, project and kind of work, and flags the points where long conversations grow costly, such as a cold cache. It can apply fixes for some findings, such as context compaction, and undo them. It needs no account and does not upload data.
Written by ooruby from the README of optimaizr 0.10.2.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
It makes the cost of long coding agent sessions visible, including the point where re-reading the conversation takes over.
What you could do with it
- Run it to see where your Claude Code tokens go and which fix to try first.
- Turn on the status line to see a countdown for the prompt cache and what returning later would cost.
- Apply the context compaction fix for Claude Code and Codex, then undo it if you change your mind.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Spend fewer tokens on the same work. A local CLI that finds wasted tokens in Claude Code, Codex and your own API calls.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.10.2, the file with digest sha512-fdQ0+vDaTH6Hi6MBlg8IF8fbYF6JUDy8ctnb3Xbj2KqTzlUHuhSevIMK4gLhWxP15YOXSReVcod5v5+ZXwl0Xw==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y optimaizr@0.10.2Pinned to 0.10.2, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- optimaizr
- Version read
- 0.10.2
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/optimaizr)About this listing
- Kind
- App
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-09
Similar apps
All appsGives your app one API for streaming from many AI model providers, with typed and validated tools.
Estimates how many tokens a text will use without loading a full tokeniser, from code or the shell.
Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.