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 skills add gotalab/cc-sdd --skill kiro-validate-gapgit 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-validate-gap)<a href="https://agentmods.dev/skills/gotalab/cc-sdd/kiro-validate-gap"><img src="https://agentmods.dev/badge/skills/gotalab/cc-sdd/kiro-validate-gap/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/skills/gotalab/cc-sdd/kiro-validate-gap"><img src="https://agentmods.dev/badge/skills/gotalab/cc-sdd/kiro-validate-gap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 55 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
- high System Prompt Leakage · line 91 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
- medium Excessive Agency · line 107 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00015 | $0.01110 |
| Opus 5.5 | $0.00006 | $0.00444 |
| Sonnet 5.5 | $0.00003 | $0.00222 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
kiro-validate-gap 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- kiro-validate-gap — 97% identical, 16 lines differ
- kiro-validate-gap — 88% identical, 78 lines differ
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Gap Validation
<background_information>
- Mission: Analyze the gap between requirements and existing codebase to inform implementation strategy
- Success Criteria:
- Comprehensive understanding of existing codebase patterns and components
- Clear identification of missing capabilities and integration challenges
- Multiple viable implementation approaches evaluated
- Technical research needs identified for design phase </background_information>
Execution Steps
-
Load Context:
- Read
{{KIRO_DIR}}/specs/$1/spec.jsonfor language and metadata - Read
{{KIRO_DIR}}/specs/$1/requirements.mdfor requirements - Core steering context:
product.md,tech.md,structure.md - Additional steering files only when directly relevant to the feature's domain rules, integrations, runtime prerequisites, compliance/security constraints, or existing product boundaries
- Use explicitly requested skills and task-relevant local skills/playbooks, including design, accessibility, and UX. Select by description and read only needed guidance, even for small tasks; preserve required checks and host/project rules.
- Read
-
Read Analysis Guidelines:
- Read
rules/gap-analysis.mdfrom this skill's directory for comprehensive analysis framework
- Read
Parallel Research
The following research areas are independent and can be executed in parallel:
- Codebase analysis: Existing implementations, architecture patterns, integration points, extension possibilities
- External dependency research: Dependency compatibility, version constraints, known integration challenges (when needed)
- Context loading: Requirements, core steering, task-relevant extra steering, relevant local agent skills/playbooks, and gap-analysis rules
If multi-agent is enabled, spawn sub-agents for each area above. Otherwise execute sequentially.
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 Changed cacd0a578841
- 1mo ago First seen · 110 lines · 15 tokens per session scan A ddace1bb02f9
kiro-validate-gap is a skill published in the GitHub repository gotalab/cc-sdd (3,745 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 1,110 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 skills, from other repositories
repo-consistency-sweep
Defect-class detection for the lower-value half of code review: convention drift, type-safety gaps, security and multi-tenant invariants, operability issues. Runs after review-hard. Checks against a curated bug-class library that grows via pr-feedback-ingest. Use when at least one slice is implemented and you want a…
pr-feedback-ingest
Turn PR feedback (Greptile, CI, bots, humans) into a traceable backlog, so the next step is a narrow implement-approved-slice. Corrective scope only. Use when a PR has review feedback to map to files and slices. Do not use for a new direction or contract (use post-review-pivot), no payload, or task-memory drift only…
review-hard
Review the current task changes for correctness, safety, and maintainability risks before slice closure or PR prep, and recommend the smallest safe next step. Use when a slice or task-level implementation was completed, the user wants a focused engineering risk review before closure or PR prep, or meaningful issues…
atom-audit-fleet
Audit every atom in parallel against the component guidelines, one worker per small group, merging rows into one ATOMAUDIT.md table (orchestrator-workers variant of atom-audit). Use when the atom count is 6 or more and COMPONENTGUIDELINES.md exists. Do not use below 6 atoms (use atom-audit single-agent), without…
verify-against-rubric-fleet
Orchestrator-workers generalization of verify-against-rubric: parallel stateless sub-agents judge one artifact each against ONE locked rubric, merged into VERIFICATIONLOG.md. Use when N >= 4 artifacts share one rubric (multi-slice retrospective, batch PR review). Do not use for single artifacts (use…
graphql-contract-review
Review a GraphQL schema and a Backend-for-Frontend (BFF) contract BEFORE implementation against a GraphQL checklist (nullability, N+1, cost limits, federation, BFF thinness). Use when designing or modifying a GraphQL schema, a federated subgraph, or a BFF contract. Do not use for a REST contract (use…