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/creategit 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.00016 | $0.03246 |
| Opus 5 | $0.00008 | $0.01623 |
| Sonnet 5 | $0.00003 | $0.00649 |
| Haiku 4.5 | $0.00002 | $0.00325 |
Grade A, and why
create 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 — 517 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unified Feature Specification (Enhanced)
Generate complete feature specification with deep codebase exploration using Task agents.
Your Task
Create a complete specification for: $ARGUMENTS
Enhanced Flow Overview
- Triage - Assess complexity, determine exploration depth
- Explore - Spawn Explore agents to understand codebase (parallel)
- Initial Questions - Gather context informed by exploration
- Plan - Spawn Plan agents for approaches and strategies (parallel)
- Synthesize - Create exploration.md with all findings
- Generate - Create context.md, requirements.md, tasks.md
- Review - Run /spec:review to validate spec before finalizing
- Summary - Present all generated files
Phase 0: Triage
Quickly assess feature complexity to determine how many Explore agents to spawn.
Assessment Steps:
- Parse the feature description for complexity keywords
- Check if
features/directory exists with established patterns:Glob("features/*/context.md") - Estimate project size:
Glob("**/*.{ts,js,py,go,rs,java}")(count source files)
Complexity Matrix:
| Indicator | Low | Medium | High |
|---|---|---|---|
| Description keywords | Simple CRUD, basic | Auth, API, data | Integration, realtime, complex |
| Existing features | 0 | 1-3 | 4+ |
| Source files | < 20 | 20-100 | > 100 |
Agent Count Decision:
- Low complexity: 1 Explore agent (comprehensive)
- Medium complexity: 2 Explore agents (patterns + similar features)
- High complexity: 3 Explore agents (patterns, similar features, tech stack)
Phase 1: Explore Agents
Use the Task tool with subagent_type: "Explore" to spawn codebase exploration agents. Run all applicable agents in parallel.
Agent 1: Patterns & Conventions (Always spawn)
Task tool parameters:
- subagent_type: "Explore"
- description: "Explore codebase patterns"
- prompt: |
Explore the codebase to understand existing patterns for implementing: [feature-description]
Search for and document:
1. Directory structure - Where does similar code live? (use Glob)
2. Naming conventions - File names, function names, class names
3. Code organization - How are modules/services/controllers structured?
4. Error handling - How are errors caught, logged, and reported?
5. Configuration - How is config managed? Environment variables?
Use Glob and Grep to find concrete examples. Return findings with specific file paths.
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 · 517 lines · 16 tokens per session scan A e80f54f3de54
create is a command published in the GitHub repository marcelsud/spec-driven-agentic-development (174 stars, last pushed 9mo ago), licensed MIT. It adds 16 tokens to every session and 3,246 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.