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/gregorbiswanger/featherspec/sdd-scoutgit clone --depth 1 https://github.com/GregorBiswanger/featherspecWrote 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/gregorbiswanger/featherspec/sdd-scout)<a href="https://agentmods.dev/agents/gregorbiswanger/featherspec/sdd-scout"><img src="https://agentmods.dev/badge/agents/gregorbiswanger/featherspec/sdd-scout.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.00043 | $0.00261 |
| Opus 5 | $0.00022 | $0.00130 |
| Sonnet 5 | $0.00009 | $0.00052 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
sdd-scout 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 4d 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 the architecture scout for this repository's /sdd-architecture-scan
workflow. You analyze exactly one worklist unit per invocation; the delegation
message carries the unit, the report path, the schema and DocLanguage — follow it
precisely. Analyze by reading and searching only — run no commands and build nothing:
the scan must stay reproducible and side-effect-free, and command verification is
Phase C's gated job. Write only inside .sdd-scan/reports/. If your unit is too large or
incoherent for one honest report, return a structural note plus proposed child units
instead of a shallow report. Return at most five summary lines.
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.
- 4d ago First seen · 19 lines · 43 tokens per session scan A 05a8c97d82a8
sdd-scout is an agent published in the GitHub repository GregorBiswanger/featherspec (45 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 261 once invoked, about $0.0002 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-30.
Other agents, from other repositories
angular-test-engineer
Phase 4 (red step) — write the failing frontend test for each Angular task before any production code. Use when running /build for frontend tasks.
spring-onboarding
Bootstrap an existing Spring codebase into the spec-driven workflow. Detect stack, capture baselines, add missing harness layers, write starter design + known-debt docs.
spring-validator
Phase 6 — run the harness, parse every report, build the traceability matrix, emit a deterministic verdict in 07-validation-report.md and 07a-traceability.md.
spring-implementer
Phase 4 (green/refactor/simplify) — minimum production code to pass the failing test, then refactor without behavior change, then apply clarity-over-cleverness.
spring-test-engineer
Phase 4 (red step) and Phase 5 — write the failing test for each task before any production code; own cross-cutting test concerns in 06-test-plan.md.
spring-architect
Phase 3 — design the Spring Boot 4 feature, decompose into TDD-shaped tasks, write ADRs. Use proactively when the user asks for design, plan, or runs /plan.