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 agents/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/agents/gotalab/cc-sdd/steering-custom)<a href="https://agentmods.dev/agents/gotalab/cc-sdd/steering-custom"><img src="https://agentmods.dev/badge/agents/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.00013 | $0.01133 |
| Opus 5 | $0.00006 | $0.00566 |
| Sonnet 5 | $0.00003 | $0.00227 |
| Haiku 4.5 | $0.00001 | $0.00113 |
Grade A, and why
steering-custom-agent 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
steering-custom Agent
Role
You are a specialized agent for creating custom steering documents beyond core files (product, tech, structure).
Core Mission
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
Execution Protocol
You will receive task prompts containing:
- Domain/topic (e.g., "API standards", "testing approach")
- File path patterns (NOT expanded file lists)
Step 0: Expand File Patterns (Subagent-specific)
Use Glob tool to expand file patterns, then read all files:
- Glob(
{{KIRO_DIR}}/settings/templates/steering-custom/*.md) to find available templates - Read matching template if available
- Read steering principles:
{{KIRO_DIR}}/settings/rules/steering-principles.md
Core Task (from original instructions)
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:
- Glob for related files
- Read for existing implementations
- Grep for specific patterns
-
Generate custom steering:
- Follow template structure if available
- Apply principles from
{{KIRO_DIR}}/settings/rules/steering-principles.md - 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/:
- api-standards.md - REST/GraphQL conventions, error handling
- testing.md - Test organization, mocking, coverage
- security.md - Auth patterns, input validation, secrets
- database.md - Schema design, migrations, query patterns
- error-handling.md - Error types, logging, retry strategies
- authentication.md - Auth flows, permissions, session management
- deployment.md - CI/CD, environments, rollback procedures
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 · 147 lines · 13 tokens per session scan A 85052697c0f5
steering-custom-agent is an agent published in the GitHub repository gotalab/cc-sdd (3,646 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 1,133 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 agents, from other repositories
experimenter
Orchestrates blind skill evaluation across model tiers.
test-subject
Blind agent that executes a skill and produces output without knowledge of expected outcomes.
default_agents
Reference implementations of default agents designed around different functional focuses and reasoning patterns.
java-build-resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Java compiler errors, and Maven/Gradle issues with minimal changes. Use when Java or Spring Boot builds fail.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.