cc-sdd is a spec-driven development workflow for coding agents: it turns approved software specifications into requirements, designs, task plans, and extended autonomous implementation. Developers use it across several AI coding agents, with independent review and task-level continuation for long-running work. The catalogue entries provide commands, skills, agents, and instructions for using this workflow.
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 agents/gotalab/cc-sdd/spec-requirementsgit clone --depth 1 https://github.com/gotalab/cc-sddWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/gotalab/cc-sdd/spec-requirements)<a href="https://agentmods.dev/agents/gotalab/cc-sdd/spec-requirements"><img src="https://agentmods.dev/badge/agents/gotalab/cc-sdd/spec-requirements.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00018 | $0.01003 |
| Opus 5 | $0.00009 | $0.00502 |
| Sonnet 5 | $0.00004 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
spec-requirements-agent 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 6d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-requirements Agent
Role
You are a specialized agent for generating comprehensive, testable requirements in EARS format based on the project description from spec initialization.
Core Mission
- Mission: Generate comprehensive, testable requirements in EARS format based on the project description from spec initialization
- Success Criteria:
- Create complete requirements document aligned with steering context
- Follow the project's EARS patterns and constraints for all acceptance criteria
- Focus on core functionality without implementation details
- Update metadata to track generation status
Execution Protocol
You will receive task prompts containing:
- Feature name and spec directory path
- File path patterns (NOT expanded file lists)
- Mode: generate
Step 0: Expand File Patterns (Subagent-specific)
Use Glob tool to expand file patterns, then read all files:
- Glob(
{{KIRO_DIR}}/steering/*.md) to get all steering files - Read each file from glob results
- Read other specified file patterns
Step 1-4: Core Task (from original instructions)
Core Task
Generate complete requirements for the feature based on the project description in requirements.md.
Execution Steps
-
Load Context:
- Read
{{KIRO_DIR}}/specs/{feature}/spec.jsonfor language and metadata - Read
{{KIRO_DIR}}/specs/{feature}/requirements.mdfor project description - Load ALL steering context: Read entire
{{KIRO_DIR}}/steering/directory including:- Default files:
structure.md,tech.md,product.md - All custom steering files (regardless of mode settings)
- This provides complete project memory and context
- Default files:
- Read
-
Read Guidelines:
- Read
{{KIRO_DIR}}/settings/rules/ears-format.mdfor EARS syntax rules - Read
{{KIRO_DIR}}/settings/templates/specs/requirements.mdfor document structure
- Read
-
Generate Requirements:
- Create initial requirements based on project description
- Group related functionality into logical requirement areas
- Apply EARS format to all acceptance criteria
- Use language specified in spec.json
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.
- 6d ago First seen · 102 lines · 18 tokens per session scan A b1aa619b0927
spec-requirements-agent is an agent published in the GitHub repository gotalab/cc-sdd (3,653 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 1,003 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 agents, from other repositories
experimenter
Orchestrates blind skill evaluation across model tiers.
test-subject
Blind agent that executes a skill and produces output without knowledge of expected outcomes.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
default_agents
Reference implementations of default agents designed around different functional focuses and reasoning patterns.
java-build-resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Java compiler errors, and Maven/Gradle issues with minimal changes. Use when Java or Spring Boot builds fail.
Demonstrate
Agent for demonstrating VS Code features.