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/kaze-jp/kusa/validate-designgit clone --depth 1 https://github.com/kaze-jp/kusaWrote 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/kaze-jp/kusa/validate-design)<a href="https://agentmods.dev/commands/kaze-jp/kusa/validate-design"><img src="https://agentmods.dev/badge/commands/kaze-jp/kusa/validate-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.00000 | $0.00520 |
| Opus 5 | $0.00000 | $0.00260 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
validate-design 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Design
Validate a design document against its requirements for completeness, consistency, and correctness.
Usage
/kiro:validate-design <feature-name>
Instructions
-
Read both documents:
.kiro/specs/$FEATURE_NAME/requirements.md.kiro/specs/$FEATURE_NAME/design.md
If either is missing, report which file is absent and what command to run.
-
Perform traceability check:
- For EVERY requirement ID in
requirements.md, verify it appears in the design's traceability section - Flag any requirement that has no corresponding design component
- Flag any design component that does not trace back to a requirement
- For EVERY requirement ID in
-
Check for gaps:
- Error handling: Does every API contract specify error cases?
- Edge cases: Are boundary conditions from requirements addressed?
- Security: Are authentication/authorization requirements covered?
- Performance: Are performance requirements reflected in design choices?
- Accessibility: Are accessibility requirements addressed?
-
Check for inconsistencies:
- Data model fields must match what API contracts reference
- Component interfaces must be compatible with their consumers
- State management must account for all state transitions in requirements
- Naming must be consistent across all design sections
-
Check design quality:
- Architecture decisions have rationale documented
- Component boundaries are clear and explicit
- No circular dependencies between components
- Testing strategy covers all components
- No premature optimization
-
Generate validation report:
# Design Validation: <feature-name>
## Traceability
- Requirements covered: X / Y
- Uncovered requirements: [list]
- Orphan design components: [list]
## Gaps Found
- [ ] <gap description with severity: Critical/Major/Minor>
## Inconsistencies Found
- [ ] <inconsistency description>
## Design Quality
- [ ] All decisions have rationale: Pass/Fail
- [ ] Component boundaries clear: Pass/Fail
- [ ] No circular dependencies: Pass/Fail
- [ ] Error handling complete: Pass/Fail
## Verdict: PASS / NEEDS REVISION
<Summary and recommended fixes>
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 · 80 lines · 0 tokens per session scan A 2939e0f24fe5
validate-design is a command published in the GitHub repository kaze-jp/kusa (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 520 tokens. 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.