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 commands/gotalab/cc-sdd/steeringgit 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/commands/gotalab/cc-sdd/steering)<a href="https://agentmods.dev/commands/gotalab/cc-sdd/steering"><img src="https://agentmods.dev/badge/commands/gotalab/cc-sdd/steering.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 | $0.00014 | $0.00435 |
| Opus 5 | $0.00007 | $0.00217 |
| Sonnet 5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
steering 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 5d 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:
- steering — 92% identical, 16 lines differ
What it actually says
Kiro Steering Management
Mode Detection
Perform detection before invoking Subagent:
Check {{KIRO_DIR}}/steering/ status:
- Bootstrap Mode: Empty OR missing core files (product.md, tech.md, structure.md)
- Sync Mode: All core files exist
Use Glob to check for existing steering files.
Invoke Subagent
Delegate steering management to steering-agent:
Use the Task tool to invoke the Subagent with file path patterns:
Task(
subagent_type="steering-agent",
description="Manage steering files",
prompt="""
Mode: {bootstrap or sync based on detection}
File patterns to read:
- {{KIRO_DIR}}/steering/*.md (if sync mode)
- {{KIRO_DIR}}/settings/templates/steering/*.md
- {{KIRO_DIR}}/settings/rules/steering-principles.md
JIT Strategy: Fetch codebase files when needed, not upfront
"""
)
Display Result
Show Subagent summary to user:
Bootstrap:
- Generated steering files: product.md, tech.md, structure.md
- Review and approve as Source of Truth
Sync:
- Updated steering files
- Code drift warnings
- Recommendations for custom steering
Notes
- All
{{KIRO_DIR}}/steering/*.mdloaded as project memory - Templates and principles are external for customization
- Focus on patterns, not catalogs
- "Golden Rule": New code following patterns shouldn't require steering updates
- Avoid documenting agent-specific tooling directories (e.g.
.cursor/,.gemini/,.claude/) {{KIRO_DIR}}/settings/content should NOT be documented in steering files (settings are metadata, not project knowledge)- Light references to
{{KIRO_DIR}}/specs/and{{KIRO_DIR}}/steering/are acceptable; avoid other.kiro/directories
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.
- 5d ago First seen · 63 lines · 14 tokens per session scan A 350b5c2ce0cb
steering is a command published in the GitHub repository gotalab/cc-sdd (3,646 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 435 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 commands, 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…
init-workspace-flow-discovery
Phase 3 Discovery of init-workspace-flow.
init-workspace-flow-questions
Phase 8 Questions of init-workspace-flow.
memory-why
Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.