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-steering-customgit 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-steering-custom)<a href="https://agentmods.dev/skills/gotalab/cc-sdd/kiro-steering-custom"><img src="https://agentmods.dev/badge/skills/gotalab/cc-sdd/kiro-steering-custom/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-steering-custom"><img src="https://agentmods.dev/badge/skills/gotalab/cc-sdd/kiro-steering-custom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01102 |
| Opus 5 | $0.00007 | $0.00551 |
| Sonnet 5 | $0.00003 | $0.00220 |
| Haiku 4.5 | $0.00001 | $0.00110 |
Grade A, and why
kiro-steering-custom 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 10d 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-steering-custom — 95% identical, 44 lines differ
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.
Kiro Custom Steering Creation
<background_information> Role: Create specialized steering documents beyond core files (product, tech, structure).
Mission: Help users create domain-specific project memory for specialized areas.
Success Criteria:
- Custom steering captures specialized patterns
- Follows same granularity principles as core steering
- Provides clear value for specific domain </background_information>
If steering context is already available from conversation, skip redundant file reads. Otherwise:
- Check
{{KIRO_DIR}}/settings/templates/steering-custom/for available templates - Read
rules/steering-principles.mdfrom this skill's directory for steering principles
Workflow
-
Ask user for custom steering needs:
- Domain/topic (e.g., "API standards", "testing approach")
- Specific requirements or patterns to document
-
Check if template exists:
- Load from
{{KIRO_DIR}}/settings/templates/steering-custom/{name}.mdif available - Use as starting point, customize based on project
- Load from
-
Analyze codebase (JIT) for relevant patterns:
Parallel Research
The following research areas are independent and can be executed in parallel:
- Template & principles: Load matching template and steering-principles.md
- Domain patterns: Analyze codebase for domain-specific patterns using Glob/Grep/Read
If multi-agent is enabled, spawn sub-agents for each area above. Otherwise execute sequentially.
After all parallel research completes, synthesize findings for steering document.
-
Generate custom steering:
- Follow template structure if available
- Apply principles from
rules/steering-principles.mdfrom this skill's directory - Focus on patterns, not exhaustive lists
- Keep to 100-200 lines (2-3 minute read)
-
Create file in
{{KIRO_DIR}}/steering/{name}.md
Available Templates
Templates available in {{KIRO_DIR}}/settings/templates/steering-custom/:
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.
- 10d ago First seen · 146 lines · 14 tokens per session scan A a2cd948a42ca
kiro-steering-custom is a skill published in the GitHub repository gotalab/cc-sdd (3,659 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 1,102 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 skills, from other repositories
compact-task-memory
Produce a lossy compaction summary of TASKSTATE.md when task memory has grown beyond a useful working size, preserving canonical decisions and recommended next step while dropping stale facts. Distinct from sync-task-state (incremental, append-only, never lossy) and state-reconcile (drift repair, no shrinking). Use…
capture-observation
Append a single observation, question, hypothesis, or concern to TASKSTATE.md as task memory without disrupting in-progress work or requiring a full state sync. Lean append-only; never restructures other artifacts. Use when something surfaces mid-work that should be remembered for later (during planning…
harvest-session-learnings
Scan the current working session and the active task's artifacts for reusable, generalizable lessons (what was tried, what failed and why, what surprised us, what the next task should do differently) and propose anchored entries to append to the task's LEARNINGS.md, the produce-side counterpart to the ADR-0017 consume…
session-summaries
What the chat right-panel session summary shows, what it costs, and how to make a session summarize well. Load when the user asks about the session summary panel, why a summary looks wrong or empty, or how to turn it on.
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.