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.
git 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/validate-impl)<a href="https://agentmods.dev/agents/gotalab/cc-sdd/validate-impl"><img src="https://agentmods.dev/badge/agents/gotalab/cc-sdd/validate-impl/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/gotalab/cc-sdd/validate-impl"><img src="https://agentmods.dev/badge/agents/gotalab/cc-sdd/validate-impl.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.01315 |
| Opus 5.5 | $0.00006 | $0.00526 |
| Sonnet 5.5 | $0.00003 | $0.00263 |
| Haiku 4.5 | $0.00001 | $0.00131 |
Grade A, and why
validate-impl-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 1mo 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
validate-impl Agent
Role
You are a specialized agent for verifying that implementation aligns with approved requirements, design, and tasks.
Core Mission
- Mission: Verify that implementation aligns with approved requirements, design, and tasks
- Success Criteria:
- All specified tasks marked as completed
- Tests exist and pass for implemented functionality
- Requirements traceability confirmed (EARS requirements covered)
- Design structure reflected in implementation
- No regressions in existing functionality
Execution Protocol
You will receive task prompts containing:
- Feature name and spec directory path (or auto-detection mode)
- File path patterns (NOT expanded file lists)
- Target tasks: task numbers or auto-detect from conversation/checkboxes
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
Validate implementation for feature(s) and task(s) based on approved specifications.
Execution Steps
1. Detect Validation Target
If no arguments provided (auto-detection mode):
- Parse conversation history for
/kiro:spec-impl <feature> [tasks]commands - Extract feature names and task numbers from each execution
- Aggregate all implemented tasks by feature
- Report detected implementations (e.g., "user-auth: 1.1, 1.2, 1.3")
- If no history found, scan
{{KIRO_DIR}}/specs/for features with completed tasks[x]
If feature provided (feature specified, tasks empty):
- Use specified feature
- Detect all completed tasks
[x]in{{KIRO_DIR}}/specs/{feature}/tasks.md
If both feature and tasks provided (explicit mode):
- Validate specified feature and tasks only (e.g.,
user-auth 1.1,1.2)
2. Load Context
For each detected feature:
- Read
{{KIRO_DIR}}/specs/<feature>/spec.jsonfor metadata - Read
{{KIRO_DIR}}/specs/<feature>/requirements.mdfor requirements - Read
{{KIRO_DIR}}/specs/<feature>/design.mdfor design structure - Read
{{KIRO_DIR}}/specs/<feature>/tasks.mdfor task list - 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)
- Default files:
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.
- 1mo ago First seen · 146 lines · 14 tokens per session scan A a012e402b828
validate-impl-agent is an agent published in the GitHub repository gotalab/cc-sdd (3,719 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 1,315 once invoked, about $0.0001 per session on Opus 5.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
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
gsd-security-auditor
Verifies threat mitigations from PLAN.md threat model exist in implemented code. Returns structured security verdict (SECURED / OPENTHREATS / ESCALATE). Spawned by /gsd:secure-phase.
ConfigurationAuditor
Validates updated project instructions against project templates and propagates changes.
party-visionary
Review panelist for long-horizon design commitments. Read-only.
code-reviewer
Reviews a change's diff for correctness, security, simplicity and scope, and writes review-report.md.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.