This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
agent-usage-guard
Stop Claude Code from spending your usage window in minutes
A Claude Code mod that holds runaway agent spend before it happens: it reads your plan's live 5-hour and weekly usage, then asks before subagent fan-out, heavy-context prompts and retry loops - and refuses when nobody can answer. Local and privacy-minimal (no network, no processes, never stores prompt text), fails open, and /agent-guard report shows what it did. MIT, one plugin install command.
Hi Product Hunt, I'm Riccardo, the maker. Thanks @quietlens for hunting it, that was a nice surprise this morning.
I built it after one prompt in June made 394 agent calls. In ten minutes they replayed 84M tokens of context. Over 60 days I hit the session limit 12 times, and it was rarely one big request. It was big contexts sent again and again, with agents multiplying them.
agent-usage-guard is a Claude Code mod. It reads your plan's live 5-hour and weekly usage and asks before:
subagents fan out, from 80% of either window or when too many start at once
a prompt resends 500k+ tokens of context (you can compact first, then send)
a retry loop goes round again after 3 identical failures
If nobody is there to answer, it refuses. It runs locally, makes no network calls and never stores your prompts. If it breaks, it gets out of the way. /agent-guard report shows everything it did.
What's the most agents you've seen one prompt start?
About agent-usage-guard on Product Hunt
“Stop Claude Code from spending your usage window in minutes”
agent-usage-guard was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #86 on the daily leaderboard. A Claude Code mod that holds runaway agent spend before it happens: it reads your plan's live 5-hour and weekly usage, then asks before subagent fan-out, heavy-context prompts and retry loops - and refuses when nobody can answer. Local and privacy-minimal (no network, no processes, never stores prompt text), fails open, and /agent-guard report shows what it did. MIT, one plugin install command.
On the analytics side, agent-usage-guard competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how agent-usage-guard performed against the three products that launched closest to it on the same day.
Who hunted agent-usage-guard?
agent-usage-guard was hunted by Casey Lee. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of agent-usage-guard including community comment highlights and product details, visit the product overview.
Casey Lee
Hi Product Hunt, I'm Riccardo, the maker. Thanks @quietlens for hunting it, that was a nice surprise this morning.
I built it after one prompt in June made 394 agent calls. In ten minutes they replayed 84M tokens of context. Over 60 days I hit the session limit 12 times, and it was rarely one big request. It was big contexts sent again and again, with agents multiplying them.
agent-usage-guard is a Claude Code mod. It reads your plan's live 5-hour and weekly usage and asks before:
subagents fan out, from 80% of either window or when too many start at once
a prompt resends 500k+ tokens of context (you can compact first, then send)
a retry loop goes round again after 3 identical failures
If nobody is there to answer, it refuses. It runs locally, makes no network calls and never stores your prompts. If it breaks, it gets out of the way. /agent-guard report shows everything it did.
To install, run these in Claude Code:
What's the most agents you've seen one prompt start?