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-gapgit 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-gap)<a href="https://agentmods.dev/commands/kaze-jp/kusa/validate-gap"><img src="https://agentmods.dev/badge/commands/kaze-jp/kusa/validate-gap.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.00577 |
| Opus 5 | $0.00000 | $0.00289 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00058 |
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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gap Analysis
Perform a gap analysis between the design document and the actual implementation.
Usage
/kiro:validate-gap <feature-name>
Instructions
-
Read the spec documents:
.kiro/specs/$FEATURE_NAME/design.md.kiro/specs/$FEATURE_NAME/tasks.md.kiro/specs/$FEATURE_NAME/requirements.md
-
Inventory the design by extracting:
- All components and their expected file locations
- All API contracts and their signatures
- All data models and their fields
- All specified error handling behaviors
- All testing requirements
-
Inventory the implementation by:
- Reading each file referenced in the design
- Checking for the existence of all specified components
- Comparing actual function signatures against API contracts
- Comparing actual data models against design specifications
- Checking for test files
-
Compare design vs implementation:
Category Check Files Do all designed files exist? Components Are all components implemented? APIs Do signatures match contracts? Data Models Do fields and validations match? Error Handling Are all error cases handled? Tests Do required tests exist and pass? Behaviors Are all specified behaviors present? -
Classify gaps:
- Missing: Designed but not implemented
- Divergent: Implemented but differs from design
- Extra: Implemented but not in design (may be fine)
- Incomplete: Partially implemented
-
Generate gap analysis report:
# Gap Analysis: <feature-name>
## Summary
- Design components: X
- Implemented: Y
- Missing: Z
- Divergent: W
## Missing Components
- [ ] <component> - <designed location>
## Divergent Implementations
- [ ] <component>: Design says <X>, implementation does <Y>
## Incomplete Implementations
- [ ] <component>: Missing <specific aspect>
## Extra Implementations
- <component>: Not in design (review needed)
## Test Coverage
- Designed tests: X
- Implemented tests: Y
- Missing tests: [list]
## Recommendations
<Prioritized list of actions to close gaps>
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 · 93 lines · 0 tokens per session scan A 9bda25d9c030
validate-gap 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 577 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.