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/felipefontoura/spec-driven-development-bookWrote 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/felipefontoura/spec-driven-development-book/reviewer)<a href="https://agentmods.dev/agents/felipefontoura/spec-driven-development-book/reviewer"><img src="https://agentmods.dev/badge/agents/felipefontoura/spec-driven-development-book/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/felipefontoura/spec-driven-development-book/reviewer"><img src="https://agentmods.dev/badge/agents/felipefontoura/spec-driven-development-book/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.00056 | $0.00348 |
| Opus 5.5 | $0.00022 | $0.00139 |
| Sonnet 5.5 | $0.00011 | $0.00070 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
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 1mo 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.
- 1mo ago First seen · 29 lines · 56 tokens per session scan A ced64ef6e5ba
reviewer is an agent published in the GitHub repository felipefontoura/spec-driven-development-book (25 stars, last pushed 5d ago), with no licence file. It adds 56 tokens to every session and 348 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
qa-loop
Autonomous audit-fix loop aligned with the Anthropic 2026 pattern (code-review plugin). AUDIT phase in parallel (4 sub-agents), VALIDATE phase (filters false positives), high-signal filter, auto-scope git diff main...HEAD. Flags --audit-only and --comment for read-only and inline PR post modes.
qa-claudemd
Audit of compliance with the project's CLAUDE.md and repo conventions. Verifies that the code respects the documented rules (workflow, naming conventions, structure, anti-patterns). Use as a sub-agent in qa-loop for the Anthropic 2026 pattern.
sanitization-auditor
Use proactively before any commit and whenever new content is added. Scans tracked files for private-project leaks - upstream private project names, internal absolute paths, proprietary domain logic (financial / portfolio / trading / prediction / tax / advisory specifics), customer data, secrets, internal endpoints…
spec-reviewer
Use when reviewing a PRD, requirements/design/tasks triplet, implementation plan, or agent prompt for completeness before code work starts. Owns requirement coverage, acceptance criteria quality, task back-references, and unresolved open questions. Triggers - "review this spec", "audit the requirements", "check this…
arbiter
Aggregates the refuter panel's independently-committed verdicts into one per-criterion verdict, under the independence guard. Never itself judges the diff. Invoked only by mnm-verify, after every lens for the current round has already committed.
refuter-correctness
Breaks a diff on pure functional correctness — wrong output, crash, violated invariant, uncovered edge case. Read-only, re-runs the decisive check itself. Invoked only by mnm-verify; never by the user, never by the implementer.