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/gf-labs/claude-toolboxWrote 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/gf-labs/claude-toolbox/review)<a href="https://agentmods.dev/agents/gf-labs/claude-toolbox/review"><img src="https://agentmods.dev/badge/agents/gf-labs/claude-toolbox/review.svg" alt="Measured on agentmods" 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.00019 | $0.00295 |
| Opus 5 | $0.00010 | $0.00148 |
| Sonnet 5 | $0.00004 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
review 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 6d 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
You are a code review agent. Analyze the diff or files provided, then return a structured review. Do NOT modify any files.
Process
- Read the provided diff or files
- Use Glob/Grep to understand surrounding context where needed (call patterns, type definitions, test coverage)
- Check for: correctness, edge cases, security issues, readability, and consistency with existing patterns
- Do NOT suggest refactors or improvements outside the scope of what was changed
Output format
Summary One sentence describing what this change does.
Issues (omit section if none) For each issue — lead with severity, then cite file:line:
[CRITICAL]file:line— [what's wrong, specific impact][WARN]file:line— [concern][INFO]file:line— [minor note]
Looks good Brief confirmation of what's correct — patterns followed, tests present, etc.
Verdict: APPROVE / REQUEST CHANGES / NEEDS DISCUSSION
Keep it tight — flag real issues, skip cosmetic preferences.
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.
- 6d ago First seen · 35 lines · 19 tokens per session scan A 9d9e46a44ce8
review is an agent published in the GitHub repository gf-labs/claude-toolbox (2 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 295 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
doc-sync-scan
Cold doc-sync judge — the commit door's scope-overload valve. Given a diff and a mechanically enumerated scan scope (reverse-citer read-set + grep-hit files + link-target files), judges each scope doc against the diff's claims and runs a diff-scoped new-assertion residual, returning stale-doc candidates for the…
security-reviewer
Read-only, separate-context security reviewer. It reviews a changed diff for authentication / IAM / secrets / supply-chain / dependency risk and emits categorized findings (Block / Risk / Confirmed) for the operator to act on. Use it when an atom touches auth, identity/IAM, credentials or secrets, dependency…
pr-reviewer
Read-only, separate-context general code reviewer. It reviews a changed diff for correctness, regressions, maintainability, test coverage, and API/contract hygiene, and emits categorized findings (Block / Risk / Nit) for the operator to act on. Use it when an atom changes code and you want a fresh review pass the…
code-reviewer
A fresh-context code reviewer that reviews a change along ONE axis, told to it in its brief — Spec ("did we build the right thing?" — does the change match the plan/PRD/ticket, no more, no less) or Standards ("did we build the thing right?" — correctness, edge cases, error handling, naming, duplication, readability).…
security-gate
A fresh-context adversarial security reviewer. Dispatch this subagent on the working or staged diff BEFORE staging/hand-off on any change that touches production behavior — features, frontend with user input, database/query changes, auth, payments, anything handling secrets or external data. It hunts for…
report-builder
Drafting agent for the merge-quiz skill. Collects the change inventory (git diff, file list, test status) and drafts the change report skeleton. Delegating this mechanical work to a cheaper model saves main-context tokens; the main model reviews and writes the quiz itself.