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 commands/lindoelio/spec-driven-steroids/spec-driven.commandgit clone --depth 1 https://github.com/lindoelio/spec-driven-steroidsWhat 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.00013 | $0.00139 |
| Opus 5 | $0.00006 | $0.00069 |
| Sonnet 5 | $0.00003 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
spec-driven.command 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 2d 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
Start Spec-Driven planning for this request:
{{args}}
Delegate this to the "Spec-Driven" agent. Select the brief lane by default or the full lane when a mandatory high-risk trigger applies. Every lane must write and validate a planning artifact, then stop for explicit human approval before implementation. The brief lane writes one brief.md and has one approval. The full lane enforces requirements → design → tasks → Red Team Review → implementation → Code Review with the existing phase gates. This toolkit has no direct lane. If the user wants execution without planning, they should use the host harness outside SDS.
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.
- 2d ago First seen · 13 lines · 13 tokens per session scan A b96642336d5e
spec-driven.command is a command published in the GitHub repository lindoelio/spec-driven-steroids (54 stars, last pushed 23d ago), licensed MIT. It adds 13 tokens to every session and 139 once invoked, about $0.0001 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 commands, from other repositories
archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
audit
Audit a file, directory, or whole repo for insecure default configuration: fallback secrets, default credentials, fail-open switches, weak crypto, permissive access, debug leakage. Parallel sweeps collect candidates, then a refuting verifier traces each one to the security decision it reaches before it is reported.
compact
Compact one or more Spec-Driven Development artifacts in place to reduce token cost on subsequent /speckit. commands. Lossless on requirements, decisions, contracts, IDs; strips template scaffolding, examples, and prose padding. The original is preserved as .full.md the first time an artifact is compacted.
concise
Toggle a project-local concise-output directive that suppresses agent prose padding during SDD steps. State lives in the project's agent memory file (AGENTS.md preferred when present, else CLAUDE.md / GEMINI.md / .cursor/rules / .windsurf/rules / etc.) inside a clearly marked block, so it is reversible and reviewable.
restore
Restore one or more Spec-Driven Development artifacts to their original (pre-compaction) state from the .full.md backups created by /compact. Deletes each backup after a successful restore.
scope
Build a focused reading manifest for the next workflow step. Names the files the agent should load, the sections it can skip, and the running token budget. Run this before /speckit.plan, /speckit.tasks, or /speckit.implement to keep their working context lean.