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

How to hold expensive Claude Code messages before they go with Optimaizr

Guard holds a message to an idle long conversation once, with its cost, and a cache countdown shows time left.

Who it is forA Claude Code user who returns to a long conversation after a break and gets a surprise bill from the first message.

The problemAfter the cache expires, the next message writes the whole conversation again, at up to twice the input price.

The outcomeExpensive messages are held once with their price, and you decide whether to send them, clear the conversation or switch to a cheaper model.

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. Run optimaizr statusline on to show the cache countdown under Claude Code's prompt.
  2. Run optimaizr guard on to hold expensive messages.
  3. When a message is held, read its cost, then send it again to go ahead or type /clear to start fresh.
  4. Run optimaizr guard to list what was held.

Prompt for your agent

In the optimaizr repo (github.com/blendbunjaku/optimaizr), run `optimaizr guard on` and then `optimaizr guard` on this machine. Report how many messages were held and the cost each would have written. Verify that a held message was not sent until it was sent again.

Caveat. Guard depends on Claude Code's own hooks, and the README does not say how it behaves in other tools.

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