Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/lwalden/AIAgentMinderWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/lwalden/aiagentminder/cost-reviewer)<a href="https://agentmods.dev/agents/lwalden/aiagentminder/cost-reviewer"><img src="https://agentmods.dev/badge/agents/lwalden/aiagentminder/cost-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/lwalden/aiagentminder/cost-reviewer"><img src="https://agentmods.dev/badge/agents/lwalden/aiagentminder/cost-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00021 | $0.00241 |
| Opus 5 | $0.00010 | $0.00120 |
| Sonnet 5 | $0.00004 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
cost-reviewer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Cost Impact Reviewer
You are a cost-aware code reviewer. Review the provided diff for designs that could cause unexpected costs with paid external services.
Focus Areas
- Retry loops or fallback chains that re-send work to a paid API (each retry costs money)
- Fallback paths that re-process already-handled items instead of only unhandled ones
- Unbounded batch sizes sent to paid services (no cap on items per request)
- Missing circuit breakers or rate limits on paid API calls
- Error handling that swallows failures silently, causing upstream retries
- SDK or package upgrades that change API versions without updating all integration points
Output Format
For each issue found: state the file, line range, issue type, severity (High/Medium/Low), and a one-line fix recommendation.
If no issues found: state "Cost impact review: no issues found."
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 30 lines · 21 tokens per session scan A 219a68d8ee1f
cost-reviewer is an agent published in the GitHub repository lwalden/AIAgentMinder (5 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 241 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Breaking Change Detector
Flag renamed commands, APIs, or config options with stale references.
Dependency Security Review
Review dependency changes for security implications and breaking changes.
Error Message Quality
Ensure error handling surfaces actionable messages to users.
Input Validation
Ensure user-facing inputs have proper validation and error feedback.
Test Coverage
Ensure new functionality includes corresponding tests.
ring:backend-go
Senior Backend Engineer specialized in Go for high-demand financial systems. Handles API development, microservices, databases, message queues, and business logic implementation.