Who it is forA developer on a Claude Pro or Max plan whose usage limits run out early and who wants to know why.
The problemIn a long session most of the spend goes to re-reading the conversation, which is hard to see from the bill.
The outcomeA ranked list of savings from your own logs, split into clear waste, likely and up to, with spend broken down by model, project and kind of work.
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
- Run
npx optimaizrin a terminal. - Read the Savings found section and the Where it goes breakdown.
- Run
optimaizr sessionsto see your costliest conversations. - Run
optimaizr whyto see spend by model, project and kind of work.
Prompt for your agent
Run `npx optimaizr` from the optimaizr repo (github.com/blendbunjaku/optimaizr) on this machine and report the Clear waste and Re-reading the conversation figures. Verify that the savings are reported per month and that the three savings tiers are not added together.
Caveat. All figures come from logs on your machine, and the README's sample numbers are the author's own usage, not yours.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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