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/validate-gapgit 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.00009 | $0.00333 |
| Opus 5 | $0.00005 | $0.00167 |
| Sonnet 5 | $0.00002 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
validate-gap 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- validate-gap — 92% identical, 14 lines differ
What it actually says
Implementation Gap Validation
Parse Arguments
- Feature name:
$1
Validate
Check that requirements have been completed:
- Verify
{{KIRO_DIR}}/specs/$1/exists - Verify
{{KIRO_DIR}}/specs/$1/requirements.mdexists
If validation fails, inform user to complete requirements phase first.
Invoke Subagent
Delegate gap analysis to validate-gap-agent:
Use the Task tool to invoke the Subagent with file path patterns:
Task(
subagent_type="validate-gap-agent",
description="Analyze implementation gap",
prompt="""
Feature: $1
Spec directory: {{KIRO_DIR}}/specs/$1/
File patterns to read:
- {{KIRO_DIR}}/specs/$1/spec.json
- {{KIRO_DIR}}/specs/$1/requirements.md
- {{KIRO_DIR}}/steering/*.md
- {{KIRO_DIR}}/settings/rules/gap-analysis.md
"""
)
Display Result
Show Subagent summary to user, then provide next step guidance:
Next Phase: Design Generation
If Gap Analysis Complete:
- Review gap analysis insights
- Run
/kiro:spec-design $1to create technical design document - Or
/kiro:spec-design $1 -yto auto-approve requirements and proceed directly
Note: Gap analysis is optional but recommended for brownfield projects to inform design decisions.
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 · 53 lines · 9 tokens per session scan A 3d54c2bf952f
validate-gap is a command published in the GitHub repository gotalab/cc-sdd (3,646 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 333 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
evaluate
Evaluate a skill across model tiers using blind testing.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
build
Run full verification pipeline.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
cost-tracker
Track session costs, understand token spend, and get optimization tips.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.