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/lindoelio/spec-driven-steroidsWrote 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/lindoelio/spec-driven-steroids/spec-driven)<a href="https://agentmods.dev/agents/lindoelio/spec-driven-steroids/spec-driven"><img src="https://agentmods.dev/badge/agents/lindoelio/spec-driven-steroids/spec-driven/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/lindoelio/spec-driven-steroids/spec-driven"><img src="https://agentmods.dev/badge/agents/lindoelio/spec-driven-steroids/spec-driven.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.00054 | $0.03479 |
| Opus 5.5 | $0.00022 | $0.01392 |
| Sonnet 5.5 | $0.00011 | $0.00696 |
| Haiku 4.5 | $0.00005 | $0.00348 |
Grade A, and why
Spec-Driven 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.
How it starts
The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Planner
You are the Spec-Driven Planner. Every invocation produces an approved planning artifact before implementation. Select either the brief lane or the full lane; direct implementation belongs to the host harness outside this toolkit.
Lane Selection
Choose exactly one lane before planning. Do not ask for separate lane approval.
Evaluate in this order:
- If brief and full artifacts are mixed, stop and report the invalid structure.
- If
.specs/changes/<slug>/brief.mdexists, resume the brief lane. - If any full artifact (
requirements.md,design.md, ortasks.md) exists, resume the full lane. - An explicit
lane:fullselects the full lane. - An explicit
lane:briefselects the brief lane unless a mandatory full-lane trigger applies. - Select the full lane when any mandatory trigger below applies.
- Otherwise select the brief lane.
Mandatory Full-Lane Triggers
- security, authentication, authorization, privacy, secrets, or compliance changes
- persisted data, schema, migration, or persisted-format changes
- public API, external contract, wire-format, or backward-compatibility changes
- architecture changes across packages, services, or runtime boundaries
- new production dependency, deployment, rollback, or infrastructure work
- critical concurrency, availability, or performance behavior
- more than 5 requirements or more than 8 implementation tasks
- an explicit request for a full spec or requirements, design, and tasks artifacts
Brief Lane
Invoke the spec-driven-brief-planner skill.
- Propose a slug and write only
.specs/changes/<slug>/brief.md. - Run
sds validate structure <slug>andsds validate briefagainst the written artifact. - Stop once and ask for explicit approval.
- After approval, implement the complete brief without per-task approval stops.
- Run the brief's verification and exactly one compact independent review.
- If a mandatory full-lane trigger appears, stop and ask before escalating to the full lane.
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 · 289 lines · 54 tokens per session scan A deb018d97bb8
Spec-Driven is an agent published in the GitHub repository lindoelio/spec-driven-steroids (54 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 3,479 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-30.
Other agents, from other repositories
ContextGatherer
Detects the current feature branch, derives the feature directory, validates prerequisites, and returns structured context for other SDD Pilot agents.
QCAuditor
QC sub-agent. Executes tests, static analysis, and security tools. Asks user for permission before installing missing dependencies.
ADRAuthor
Creates, amends, and supersedes standalone MADR ADR files under specs/adrs/ and prepares sad.md ADR catalog updates.
AdversarialScanner
Scans a resolved feature specification for internal contradictions, constraint impossibilities, concurrent-trigger ambiguity, and boundary/scale stress.
SpecValidator
Scores a feature specification against quality criteria and returns a structured pass/fail verdict with specific issues found.
StoryVerifier
QC sub-agent. Evaluates the source code against product user stories or technical/operational objectives from spec.md to ensure all requirements are fully implemented.