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/serpro69/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/serpro69/claude-toolbox/architecture-reviewer)<a href="https://agentmods.dev/agents/serpro69/claude-toolbox/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/serpro69/claude-toolbox/architecture-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/serpro69/claude-toolbox/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/serpro69/claude-toolbox/architecture-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.00087 | $0.01347 |
| Opus 5.5 | $0.00035 | $0.00539 |
| Sonnet 5.5 | $0.00017 | $0.00269 |
| Haiku 4.5 | $0.00009 | $0.00135 |
Grade A, and why
architecture-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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago Changed · +1 lines 8e5ff51469ea
- 1mo ago Changed · +21 tokens per session 69cba56bccb1
- 1mo ago First seen · 82 lines · 66 tokens per session scan A 2c0bb67a5fdf
architecture-reviewer is an agent published in the GitHub repository serpro69/claude-toolbox (151 stars, last pushed yesterday), with no licence file. It adds 87 tokens to every session and 1,347 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other agents, from other repositories
code-reviewer
Use this agent when the user has recently written or modified code and wants feedback on code quality, design, potential bugs, or architectural improvements. This agent should be invoked proactively after logical chunks of work are completed, such as: Example 1: user: "I've just implemented the book rating feature…
java-backend
Java Backend Execution Agent (Spring Boot / Quarkus).
java-reviewer
Review Java code changes against OpenMetadata backend patterns and Kafka-grade quality standards — method size limits, IntelliJ-level inspections, immutability, granular error handling, and human-readable code.
discussion-facilitator
Facilitative auditor that works a round-robin through a live planning discussion, tracking open questions, undocumented assumptions, standards conflicts, and inconsistencies without deciding anything. Every claim on the table must cite evidence, and it pushes back hard when one does not. Use when a planning…
skill-files-reviewer
Reviews supporting files (scripts, references, assets) that sit next to a SKILL.md. Use proactively after adding or changing any file in skills/ / other than SKILL.md itself.
plinth-java-coder
Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.