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 skills/gotalab/cc-sdd/kiro-debugnpx skills add gotalab/cc-sdd --skill kiro-debuggit 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/skills/gotalab/cc-sdd/kiro-debug)<a href="https://agentmods.dev/skills/gotalab/cc-sdd/kiro-debug"><img src="https://agentmods.dev/badge/skills/gotalab/cc-sdd/kiro-debug.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.00033 | $0.01194 |
| Opus 5 | $0.00016 | $0.00597 |
| Sonnet 5 | $0.00007 | $0.00239 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
kiro-debug 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- kiro-debug — 86% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kiro-debug
<background_information> This skill is for fresh-context root cause investigation. It combines local evidence, runtime/config inspection, and external documentation or issue research when available. It is not a patch generator for guess-first debugging. </background_information>
- Implementer reports
BLOCKED - Reviewer rejection repeats after remediation
- Validation fails unexpectedly
- A task appears to conflict with runtime or platform reality
- The same failure survives more than one attempted fix
Do not use this skill to speculate about fixes before gathering evidence.
Inputs
Provide:
- Exact failure symptom or blocker statement
- Error messages, stack trace, and failing command output
- Current
git diffor summary of uncommitted failed changes - Task brief: what was being built
- Reviewer feedback, if the failure came from review rejection
- Relevant spec file paths (
requirements.md,design.md) - Relevant requirement/design section numbers
- Relevant
## Implementation Notes - Runtime or environment constraints already known
Outputs
Return:
ROOT_CAUSECATEGORYFIX_PLANVERIFICATIONNEXT_ACTION: RETRY_TASK | BLOCK_TASK | STOP_FOR_HUMANCONFIDENCE: HIGH | MEDIUM | LOWNOTES
Use the language specified in spec.json.
Method
1. Read the Error Carefully
Extract:
- Exact error text
- Stack trace or failure location
- The command that produced the failure
- Whether the failure is deterministic or intermittent
2. Inspect Local Runtime and Repository State
Inspect the repository for local evidence:
package.json,pyproject.toml,go.mod,Makefile,README*- Build config
tsconfigor equivalent language/runtime config- Runtime-specific config
- Dependency versions and scripts
- Relevant changed files from
git diff
3. Search the Web if Available
If web access is available, search:
- The exact error message
- The technology + symptom combination
- Official documentation
- Version-specific issue trackers or migration notes
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 153 lines · 33 tokens per session scan A c5ce75a0f76d
kiro-debug is a skill published in the GitHub repository gotalab/cc-sdd (3,652 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 1,194 once invoked, about $0.0002 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 skills, from other repositories
todo-for-ai-agent-runtime
Runtime integration skill for external agents connecting to Todo for AI over HTTP API Token / Agent Key, including auth, task lease, events, commit, and task logs.
implementation-plan
Define an incremental, reviewable, production-safe implementation plan for the active task and persist it as IMPLEMENTATIONPLAN.md plus a TASKSTATE.md update. Breaks work into the smallest safe slices with objective, exact scope, ordering rationale, key risks, validation approach, exit criteria, and work complexity…
slice-closure
Decide whether the current slice is ready to close, distinguishing slice completion from full task completion, then persist the result in slice notes and TASKSTATE.md as explicit reviewable closure notes. For single-slice tasks may route directly to delivery. Returns no-op when slice memory would not materially…
task-close
Perform the terminal task lifecycle transition for a finished task: verify the spec done-conditions, set TASKSTATE.md to its final closed state, and move the task folder from active/ to archive/. The symmetric counterpart to task-init and the only official way to close a whole task. Use when every slice is closed, the…
task-init
Initialize the official task folder and base task memory inside projects/ /active/YYYY-MM-DD /. Creates README.md, TASKSTATE.md, SOURCEOFTRUTH.md, DECISIONS.md, IMPLEMENTATIONPLAN.md; seeds from PROJECTCHARTER.md when present; emits a multi-repo ## Repositories section in SOURCEOFTRUTH.md when 2+ repos are provided.…
autonomous-run
Drive an approved, waved IMPLEMENTATIONPLAN through the autonomous delivery track. A thin dispatcher over the existing fleet primitives (the Workflow tool, implement-approved-slice as single writer) bounded by two human gates and a runtime governor. Runs verifiable slices with little supervision and emits PROPOSED…