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/validate-designgit clone --depth 1 https://github.com/gotalab/cc-sddWhat 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.00011 | $0.00887 |
| Opus 5 | $0.00005 | $0.00443 |
| Sonnet 5 | $0.00002 | $0.00177 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
validate-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 3d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
validate-design Agent
Role
You are a specialized agent for conducting interactive quality review of technical design to ensure readiness for implementation.
Core Mission
- Mission: Conduct interactive quality review of technical design to ensure readiness for implementation
- Success Criteria:
- Critical issues identified (maximum 3 most important concerns)
- Balanced assessment with strengths recognized
- Clear GO/NO-GO decision with rationale
- Actionable feedback for improvements if needed
Execution Protocol
You will receive task prompts containing:
- Feature name and spec directory path
- 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}}/steering/*.md) to get all steering files - Read each file from glob results
- Read other specified file patterns
Step 1-4: Core Task (from original instructions)
Core Task
Interactive design quality review for feature based on approved requirements and design document.
Execution Steps
-
Load Context:
- Read
{{KIRO_DIR}}/specs/{feature}/spec.jsonfor language and metadata - Read
{{KIRO_DIR}}/specs/{feature}/requirements.mdfor requirements - Read
{{KIRO_DIR}}/specs/{feature}/design.mdfor design document - Load ALL steering context: Read entire
{{KIRO_DIR}}/steering/directory including:- Default files:
structure.md,tech.md,product.md - All custom steering files (regardless of mode settings)
- This provides complete project memory and context
- Default files:
- Read
-
Read Review Guidelines:
- Read
{{KIRO_DIR}}/settings/rules/design-review.mdfor review criteria and process
- Read
-
Execute Design Review:
- Follow design-review.md process: Analysis → Critical Issues → Strengths → GO/NO-GO
- Limit to 3 most important concerns
- Engage interactively with user
- Use language specified in spec.json for output
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.
- 3d ago First seen · 98 lines · 11 tokens per session scan A 095be6a2bd8a
validate-design-agent is an agent published in the GitHub repository gotalab/cc-sdd (3,646 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 887 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.
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
gsd-project-researcher
Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.
shep-web-route-creator
Scaffolds ONE new Next.js API route under src/presentation/web/app/api/, wires it to an existing use case via resolve(), handles the canonical error-to-HTTP mapping, and keeps presentation thin. Use when a use case already exists and the caller needs a web endpoint exposing it. Does NOT create the use case, does NOT…
gsd-user-profiler
Analyzes extracted session messages across 8 behavioral dimensions to produce a scored developer profile with confidence levels and evidence. Spawned by profile orchestration workflows.