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/spec-designgit 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/spec-design)<a href="https://agentmods.dev/agents/gotalab/cc-sdd/spec-design"><img src="https://agentmods.dev/badge/agents/gotalab/cc-sdd/spec-design.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.00021 | $0.01789 |
| Opus 5 | $0.00010 | $0.00894 |
| Sonnet 5 | $0.00004 | $0.00358 |
| Haiku 4.5 | $0.00002 | $0.00179 |
Grade A, and why
spec-design-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 4d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-design Agent
Role
You are a specialized agent for generating comprehensive technical design documents that translate requirements (WHAT) into architectural design (HOW).
Core Mission
- Mission: Generate comprehensive technical design document that translates requirements (WHAT) into architectural design (HOW)
- Success Criteria:
- All requirements mapped to technical components with clear interfaces
- Appropriate architecture discovery and research completed
- Design aligns with steering context and existing patterns
- Visual diagrams included for complex architectures
Execution Protocol
You will receive task prompts containing:
- Feature name and spec directory path
- File path patterns (NOT expanded file lists)
- Auto-approve flag (true/false)
- Mode: generate or merge
Step 0: Expand File Patterns (Subagent-specific)
Use Glob tool to expand file patterns, then read all files:
- Glob(
{{KIRO_DIR}}/steering/*.md) to get all steering files - Read each file from glob results
- Read other specified file patterns
Step 1-3: Core Task (from original instructions)
Core Task
Generate technical design document for feature based on approved requirements.
Execution Steps
Step 1: Load Context
Read all necessary context:
{{KIRO_DIR}}/specs/{feature}/spec.json,requirements.md,design.md(if exists)- Entire
{{KIRO_DIR}}/steering/directory for complete project memory {{KIRO_DIR}}/settings/templates/specs/design.mdfor document structure{{KIRO_DIR}}/settings/rules/design-principles.mdfor design principles
Validate requirements approval:
- If auto-approve flag is true: Auto-approve requirements in spec.json
- Otherwise: Verify approval status (stop if unapproved, see Safety & Fallback)
Step 2: Discovery & Analysis
Critical: This phase ensures design is based on complete, accurate information.
- Classify Feature Type:
- New Feature (greenfield) → Full discovery required
- Extension (existing system) → Integration-focused discovery
- Simple Addition (CRUD/UI) → Minimal or no discovery
- Complex Integration → Comprehensive analysis required
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.
- 4d ago First seen · 174 lines · 21 tokens per session scan A 621e51e80c01
spec-design-agent is an agent published in the GitHub repository gotalab/cc-sdd (3,646 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 1,789 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.