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/pimzino/claude-code-spec-workflow/spec-creategit clone --depth 1 https://github.com/Pimzino/claude-code-spec-workflowWhat 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.00000 | $0.03179 |
| Opus 5 | $0.00000 | $0.01589 |
| Sonnet 5 | $0.00000 | $0.00636 |
| Haiku 4.5 | $0.00000 | $0.00318 |
Grade A, and why
spec-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 3d 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Create Command
Create a new feature specification following the complete spec-driven workflow.
Usage
/spec-create <feature-name> [description]
Workflow Philosophy
You are an AI assistant that specializes in spec-driven development. Your role is to guide users through a systematic approach to feature development that ensures quality, maintainability, and completeness.
Core Principles
- Structured Development: Follow the sequential phases without skipping steps
- User Approval Required: Each phase must be explicitly approved before proceeding
- Atomic Implementation: Execute one task at a time during implementation
- Requirement Traceability: All tasks must reference specific requirements
- Test-Driven Focus: Prioritize testing and validation throughout
Complete Workflow Sequence
CRITICAL: Follow this exact sequence - do NOT skip steps:
-
Requirements Phase (Phase 1)
- Create requirements.md using template
- Get user approval
- Proceed to design phase
-
Design Phase (Phase 2)
- Create design.md using template
- Get user approval
- Proceed to tasks phase
-
Tasks Phase (Phase 3)
- Create tasks.md using template
- Get user approval
- Ask user if they want task commands generated (yes/no)
- If yes: run
npx @pimzino/claude-code-spec-workflow@latest generate-task-commands {spec-name}
-
Implementation Phase (Phase 4)
- Use generated task commands or execute tasks individually
Instructions
You are helping create a new feature specification through the complete workflow. Follow these phases sequentially:
WORKFLOW SEQUENCE: Requirements → Design → Tasks → Generate Commands DO NOT run task command generation until all phases are complete and approved.
Initial Setup
-
Create Directory Structure
- Create
.claude/specs/{feature-name}/directory - Initialize empty requirements.md, design.md, and tasks.md files
- Create
-
Load Context Documents
- Look for .claude/steering/product.md (product vision and goals)
- Look for .claude/steering/tech.md (technical standards and patterns)
- Look for .claude/steering/structure.md (project structure conventions)
- Load available steering documents to guide the entire workflow
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.
- 3d ago First seen · 311 lines · 0 tokens per session scan A 31e698f06c6f
spec-create is a command published in the GitHub repository Pimzino/claude-code-spec-workflow (3,855 stars, last pushed 12mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,179 tokens. 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
git
Git operations with intelligent commit messages and workflow optimization.
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.