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-executegit 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.01693 |
| Opus 5 | $0.00000 | $0.00847 |
| Sonnet 5 | $0.00000 | $0.00339 |
| Haiku 4.5 | $0.00000 | $0.00169 |
Grade A, and why
spec-execute 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 yesterday.
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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Execute Command
Execute specific tasks from the approved task list.
Usage
/spec-execute [task-id] [feature-name]
Phase Overview
Your Role: Execute tasks systematically with validation
This is Phase 4 of the spec workflow. Your goal is to implement individual tasks from the approved task list, one at a time.
Instructions
Agent-Based Execution (Recommended): If the spec-task-executor agent is available, use it for optimal task implementation:
Use the spec-task-executor agent to implement the specified task for the {feature-name} specification.
The agent should:
1. Load all specification context from .claude/specs/{feature-name}/
2. Load steering documents from .claude/steering/ (if available)
3. Implement ONLY the specified task
4. Follow all project conventions and leverage existing code
5. Mark the task as complete in tasks.md
6. Provide a completion summary
Context files to load:
- .claude/specs/{feature-name}/requirements.md
- .claude/specs/{feature-name}/design.md
- .claude/specs/{feature-name}/tasks.md
- .claude/steering/product.md (if exists)
- .claude/steering/tech.md (if exists)
- .claude/steering/structure.md (if exists)
Task to implement: {task-id}
Manual Execution (Fallback): If the agent is not available, follow this process:
-
Prerequisites
- Ensure tasks.md exists and is approved
- Load the spec documents from
.claude/specs/{feature-name}/:- Load
.claude/specs/{feature-name}/requirements.mdfor feature requirements - Load
.claude/specs/{feature-name}/design.mdfor technical design - Load
.claude/specs/{feature-name}/tasks.mdfor the complete task list
- Load
- Load all steering documents (if available):
- Load .claude/steering/product.md for product context
- Load .claude/steering/tech.md for technical patterns
- Load .claude/steering/structure.md for project conventions
- Identify the specific task to execute
-
Process
- Load spec documents from
.claude/specs/{feature-name}/directory:- Load requirements.md, design.md, and tasks.md for complete context
- Execute ONLY the specified task (never multiple tasks)
- Implement following existing code patterns and conventions
- Validate implementation against referenced requirements
- Run tests and checks if applicable
- CRITICAL: Mark task as complete by changing [ ] to [x] in tasks.md
- Confirm task completion status to user
- CRITICAL: Stop and wait for user review before proceeding
- Load spec documents from
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.
- yesterday First seen · 197 lines · 0 tokens per session scan A 0e43dec6f49a
spec-execute is a command published in the GitHub repository Pimzino/claude-code-spec-workflow (3,853 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,693 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
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.