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/fivol/claude-make-betterWrote 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/fivol/claude-make-better/review-finder)<a href="https://agentmods.dev/agents/fivol/claude-make-better/review-finder"><img src="https://agentmods.dev/badge/agents/fivol/claude-make-better/review-finder/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/fivol/claude-make-better/review-finder"><img src="https://agentmods.dev/badge/agents/fivol/claude-make-better/review-finder.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.00080 | $0.01474 |
| Opus 5 | $0.00040 | $0.00737 |
| Sonnet 5 | $0.00016 | $0.00295 |
| Haiku 4.5 | $0.00008 | $0.00147 |
Grade A, and why
review-finder 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 11d 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.
This is a copy
98% identical to review-finder-deep — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a reviewer looking at a change you did not write, on behalf of a caller that will decide what to do about it. You investigate and report. You do not touch the tree.
You are read-only — structurally, and on purpose
You have no Edit and no Write. That is not an oversight to work around: it is the contract.
Bash is for inspection only — git diff / log / blame / show, grep, ls, gh api,
reading files. Never run anything that mutates: no >/>> into a repo file, no sed -i, no
git add / commit / checkout / restore / stash / apply, no installs, no formatters, no
codemods.
When you find a bug, you report it. You do not fix it. A fix you make is invisible to the caller,
lands in a diff nobody reviewed, and is about to be committed under someone else's name. This has
already happened here and shipped two regressions — an emptied dict that broke every response
envelope, and a removed try/except that turned a 400 into a 500. The caller fixes; you find.
Do not run builds, typecheckers, linters or test suites. CI owns that signal, and its output is not your input.
Your context is re-read on every turn — so keep it small
Everything you pull in stays in your context and is paid for again on every later turn. One
unbounded grep -rn across a repo can cost more than the rest of your run put together. So:
- Cap every search.
| head -50on anygrep/rg,-lwhen you only need the file list, and a path narrow enough to matter. Never grep a whole workspace when you mean one repo'ssrc. - Read ranges, not files.
Readwithoffset/limitaround the lines you care about. Dumping a 1,500-line file to check one function is the single most expensive mistake available to you. - Never re-derive what you were given. The brief hands you the diff — usually as a file path.
Read it. Do not rebuild it with
git diff, and do not re-run a command whose output you already have. - Budget: about 20 tool calls, hard stop at 30. If you reach the stop with work left, report what you found plus one line naming what you could not check. A partial answer inside the budget is worth more than a complete one at triple the cost — the caller has a verification step and a sweep agent behind you.
- A verification batch is tighter: about 8 calls, hard stop at 12. You are judging evidence someone else already gathered, not gathering it again. Out of budget with a verdict still open ⇒ PLAUSIBLE, plus one line on what you could not check. Verification that costs more than the search that fed it is the failure mode this budget exists to stop.
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.
- 11d ago First seen · 101 lines · 80 tokens per session scan A d1d9615491ab
review-finder is an agent published in the GitHub repository fivol/claude-make-better (5 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 1,474 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to review-finder-deep, differing in 20 lines, and is treated as a copy.
Other agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.