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/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/commands/gotalab/cc-sdd/steering-custom)<a href="https://agentmods.dev/commands/gotalab/cc-sdd/steering-custom"><img src="https://agentmods.dev/badge/commands/gotalab/cc-sdd/steering-custom.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.00008 | $0.00403 |
| Opus 5 | $0.00004 | $0.00201 |
| Sonnet 5 | $0.00002 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
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 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-custom — 92% identical, 10 lines differ
What it actually says
Kiro Custom Steering Creation
Interactive Workflow
This command starts an interactive process with the Subagent:
- Subagent asks user for domain/topic
- Subagent checks for available templates
- Subagent analyzes codebase for relevant patterns
- Subagent generates custom steering file
Invoke Subagent
Delegate custom steering creation to steering-custom-agent:
Use the Task tool to invoke the Subagent with file path patterns:
Task(
subagent_type="steering-custom-agent",
description="Create custom steering",
prompt="""
Interactive Mode: Ask user for domain/topic
File patterns to read:
- {{KIRO_DIR}}/settings/templates/steering-custom/*.md
- {{KIRO_DIR}}/settings/rules/steering-principles.md
JIT Strategy: Analyze codebase for relevant patterns as needed
"""
)
Display Result
Show Subagent summary to user:
- Custom steering file created
- Template used (if any)
- Codebase patterns analyzed
- Content overview
Available Templates
Available templates in {{KIRO_DIR}}/settings/templates/steering-custom/:
- api-standards.md, testing.md, security.md, database.md
- error-handling.md, authentication.md, deployment.md
Notes
- Subagent will interact with user to understand needs
- Templates are starting points, customized for project
- All steering files loaded as project memory
- Avoid documenting agent-specific tooling directories (e.g.
.cursor/,.gemini/,.claude/) {{KIRO_DIR}}/settings/content should NOT be documented (it's 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 · 60 lines · 8 tokens per session scan A b670db5856c9
steering-custom is a command published in the GitHub repository gotalab/cc-sdd (3,652 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 403 once invoked, about $0.0000 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
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…
release-plan
Design a pre-deploy release and rollout strategy for a change: pick the rollout pattern (feature flag, canary, blue-green, or full progressive delivery) by risk and infra, then specify the exposure ramp, the promotion metric and threshold that advances each step, and the rollback trigger and mechanism. Produces…
repo-consistency-sweep
Proactive defect-class detection that handles the lower-value half of code review (per Bacchelli and Bird 2013) so human reviewers stay focused on design, intent, and knowledge transfer. Catches convention drift, ordering bugs, type-safety gaps, security and multi-tenant invariants (CWE-grounded), and operability…
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.