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/marcelsud/spec-driven-agentic-development/helpgit clone --depth 1 https://github.com/marcelsud/spec-driven-agentic-developmentWhat 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.00010 | $0.00680 |
| Opus 5 | $0.00005 | $0.00340 |
| Sonnet 5 | $0.00002 | $0.00136 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
help 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Development Help
Quick reference for the spec:driven development methodology.
Available Commands
| Command | Description |
|---|---|
/spec:create [feature] |
Generate complete specification with codebase exploration |
/spec:execute [feature] |
Execute implementation from tasks.md |
/spec:status |
Show implementation status of all features |
/spec:list |
List all available features |
/spec:review [feature] |
Review spec for EARS compliance and quality |
/spec:diagram [feature] |
Generate Mermaid diagrams from spec |
/spec:next |
Suggest next feature to work on |
/spec:help |
Display this help |
Workflow
/spec:create [feature] → exploration.md + context.md + requirements.md + tasks.md
/spec:review [feature] → Quality review + optional fixes
/spec:diagram [feature] → Mermaid diagrams in diagrams.md
/spec:next → Recommendation for next feature
/spec:execute [feature] → Implementation following TDD
/spec:create Flow (Enhanced)
- Triage - Assess complexity, determine exploration depth
- Explore - Spawn agents to analyze codebase patterns (parallel)
- Questions - Context-aware questions informed by exploration
- Plan - Spawn agents for approaches and strategies (parallel)
- Synthesize - Create exploration.md with findings
- Generate - Create context.md, requirements.md, tasks.md
EARS Requirements Format
| Type | Template |
|---|---|
| Ubiquitous | "The system SHALL [requirement]" |
| Event-Driven | "WHEN [trigger] THEN the system SHALL [response]" |
| State-Driven | "WHILE [state] the system SHALL [requirement]" |
| Conditional | "IF [condition] THEN the system SHALL [requirement]" |
| Optional | "WHERE [feature] the system SHALL [requirement]" |
TDD Cycle
- Red: Write failing test
- Green: Minimal code to pass
- Refactor: Improve while green
File Structure
features/[feature-name]/
├── exploration.md # Codebase analysis + approach evaluation
├── context.md # Context + technical decisions
├── requirements.md # EARS requirements
├── tasks.md # TDD implementation tasks
├── diagrams.md # Generated Mermaid diagrams (optional)
└── review.md # Spec quality review (optional)
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 · 98 lines · 10 tokens per session scan A 0b4209a4ad69
help is a command published in the GitHub repository marcelsud/spec-driven-agentic-development (174 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 680 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.