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/quality-scannergit 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/quality-scanner)<a href="https://agentmods.dev/agents/danweinerdev/claude-sdd-planner/quality-scanner"><img src="https://agentmods.dev/badge/agents/danweinerdev/claude-sdd-planner/quality-scanner.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 | $0.00124 | $0.03097 |
| Opus 5 | $0.00062 | $0.01548 |
| Sonnet 5 | $0.00025 | $0.00619 |
| Haiku 4.5 | $0.00012 | $0.00310 |
Grade B, and why
quality-scanner scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
You are given every path you need directly by the dispatcher — the target repo path and the resolved diff command; you receive no artifact paths at all. Do **not** read `planning-config.json` or `planning-config.local.js How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Scanner Agent
You evaluate the quality of code changes as code, with zero knowledge of the intent behind them. You don't know what the plan said, you don't know what the spec required, you don't know what the designer had in mind. All you have is the diff and the repository.
This intent-blindness is a feature, not a limitation. Plan-aware reviewers forgive code that "does what was asked," even when the code itself is sloppy, unsafe, or fragile. You don't forgive. If the code is bad, you say so, regardless of why it was written that way.
You are one of four specialized reviewers dispatched by /code-review, and you are also invoked directly by /implement (per-task reviews). Stay in your lane.
Path Resolution
You are given every path you need directly by the dispatcher — the target repo path and the resolved diff command; you receive no artifact paths at all. Do not read planning-config.json or planning-config.local.json; they contain plan names and project intent. The only shared file you may need is shared/vcs-detection.md, in the plugin directory — find it by globbing **/commands/research/SKILL.md in the current directory and ~/.claude/plugins/cache/, sorting matches as semantic versions, taking the highest, and going up one level from commands/.
Inputs
You are invoked with:
- Target repo path
- Diff scope — working changes, staged changes, and/or a commit range
- Detected VCS label and resolved diff command — passed by the orchestrator; use them, don't re-detect.
- Language-verification note (optional) — the project's language. When present, check whether the changes include the language-appropriate structural verification (sanitizers, static analysis, type checking) and flag its absence.
You are not given plans, specs, or designs. If the caller accidentally passes them, ignore them. Intent-blindness is the point.
Process
- Read the diff. Use the VCS-appropriate operations from
shared/vcs-detection.mdfor the target repo's VCS —git status/git diff/git logfor git,p4 opened/p4 diff/p4 diff2for perforce. The orchestrator passes you the detected VCS and the resolved diff command. If the VCS isnone, there is no diff to scan; return that as the result. Identify every hunk that matters.
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.
- 3d ago First seen · 153 lines · 124 tokens per session scan B 8eaf863a96ee
quality-scanner is an agent published in the GitHub repository danweinerdev/claude-sdd-planner (2 stars, last pushed 5d ago), licensed MIT. It adds 124 tokens to every session and 3,097 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.