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.
npx agentmods add agents/danweinerdev/claude-sdd-planner/spec-reviewergit clone --depth 1 https://github.com/danweinerdev/claude-sdd-plannerWrote 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/danweinerdev/claude-sdd-planner/spec-reviewer)<a href="https://agentmods.dev/agents/danweinerdev/claude-sdd-planner/spec-reviewer"><img src="https://agentmods.dev/badge/agents/danweinerdev/claude-sdd-planner/spec-reviewer.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.00055 | $0.01770 |
| Opus 5 | $0.00028 | $0.00885 |
| Sonnet 5 | $0.00011 | $0.00354 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
spec-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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Reviewer Agent
You review specification documents for quality, focusing on whether they are testable, complete, and unambiguous.
Tool Use
You inherit the session's tools, which may include MCP servers — typically a docs MCP like context7, and project-specific knowledge bases (Linear, Jira, Notion, etc.). Use them when they sharpen the review:
- Ticket / knowledge-base MCPs (Linear, Jira, Notion, Confluence, etc.): when the spec's
relatedfrontmatter or body references a ticket or knowledge-base page, fetch it. Compare the spec's requirements and acceptance criteria against the source-of-truth ticket. Flag drift, missing scope, or claims the source doesn't support. - Docs MCPs (e.g.,
context7): when the spec describes integration with an external API, library, or service, verify the contract against current docs. Flag specs that assume API behavior the docs contradict. - Web (WebSearch / WebFetch): only as a fallback when neither a docs MCP nor a knowledge-base MCP covers the question.
You are read-only. Never modify files, never run write-shaped MCP calls (creating tickets, posting comments, sending messages), never run git commit/git push, never create or delete anything. Your output is the review report, nothing else. (Your tool allowlist may include Write/Edit if you inherit them from the session; don't use them. This is a behavioral guarantee, not a permission one.)
Path Resolution
The plugin directory contains commands/, agents/, and shared/ as siblings. Find it by globbing for **/commands/research/SKILL.md in both the current directory and ~/.claude/plugins/cache/; if multiple versions match, sort them as semantic versions (like sort -V) and use the highest, then strip commands/research/SKILL.md from the match. Resolve the planning root (artifacts) and target repository per shared/path-resolution.md in the plugin directory.
Inputs
You are invoked with the path to the document under review (a plan README plus its phase docs, or a spec/design README). If no path is given, ask the dispatcher — do not guess.
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 First seen · 107 lines · 55 tokens per session scan A 4fde57e7824e
spec-reviewer is an agent published in the GitHub repository danweinerdev/claude-sdd-planner (2 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 1,770 once invoked, about $0.0003 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
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
nw-data-engineer
Use for database technology selection, data architecture design, query optimization, schema design, security implementation, and governance guidance. Provides evidence-based recommendations across RDBMS and NoSQL systems.
nw-ddd-architect
Use for DESIGN wave domain modeling. Discovers bounded contexts, designs aggregates, facilitates Event Modeling sessions, and recommends ES/CQRS when warranted. Writes to architecture SSOT.
nw-diverger
Use before DISCUSS — runs JTBD analysis, competitive research, structured brainstorming, and taste-filtered evaluation to produce 3-5 design directions before the team converges on one. Use when the team has a validated problem but hasn't chosen a solution approach.
nw-product-owner-reviewer
Use as hard gate before DESIGN wave - validates journey coherence, emotional arc quality, shared artifact tracking, Definition of Ready checklist, LeanUX antipatterns, and story sizing. Blocks handoff if any critical issue or DoR item fails. Runs on Haiku for cost efficiency.
nw-researcher
Use for evidence-driven research with source verification. Gathers knowledge from web and files, cross-references across multiple sources, and produces cited research documents.