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/kbwo/ccmanager/validate-gapgit clone --depth 1 https://github.com/kbwo/ccmanagerWhat 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.01253 |
| Opus 5 | $0.00005 | $0.00626 |
| Sonnet 5 | $0.00002 | $0.00251 |
| Haiku 4.5 | $0.00001 | $0.00125 |
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 yesterday.
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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Gap Validation
Analyze implementation requirements and existing codebase for feature: $1
Context Validation
Steering Context
- Architecture context: @.kiro/steering/structure.md
- Technical constraints: @.kiro/steering/tech.md
- Product context: @.kiro/steering/product.md
- Custom steering: Load all "Always" mode custom steering files from .kiro/steering/
Existing Spec Context
- Current spec directory: !
bash -c 'ls -la .kiro/specs/$1/ 2>/dev/null || echo "No spec directory found"' - Requirements document: @.kiro/specs/$1/requirements.md
- Spec metadata: @.kiro/specs/$1/spec.json
Task: Implementation Gap Analysis
Prerequisites
- Requirements document must exist:
.kiro/specs/$1/requirements.md - If not exist, stop with message: "Run
/kiro:spec-requirements $1first to generate requirements"
Analysis Process
1. Current State Investigation
Existing Codebase Analysis:
- Identify files and modules related to the feature domain
- Map current architecture patterns, conventions, and tech stack usage
- Document existing services, utilities, and reusable components
- Understand current data models, APIs, and integration patterns
Code Structure Assessment:
- Document file organization, naming conventions, and architectural layers
- Extract import/export patterns and module dependency structures
- Identify existing testing patterns (file placement, frameworks, mocking approaches)
- Map API client, database, and authentication implementation approaches currently used
- Note established coding standards and development practices
2. Requirements Feasibility Analysis
Technical Requirements Extraction:
- Parse EARS format requirements from requirements.md
- Identify technical components needed for each requirement
- Extract non-functional requirements (security, performance, etc.)
- Map business logic complexity and integration points
Gap Identification:
- Missing technical capabilities vs requirements
- Unknown technologies or external dependencies
- Potential integration challenges with existing systems
- Areas requiring research or proof-of-concept work
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.
- yesterday First seen · 156 lines · 9 tokens per session scan A 9adbb60ada11
validate-gap is a command published in the GitHub repository kbwo/ccmanager (1,229 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 1,253 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
package-assistant
Convert an OfficeCLI skill into a fully wired AionUi assistant preset, or update an existing one.
implement
Have Gemini (via agy) implement a task by editing files directly.
adversarial-review
Get a devil's advocate review that challenges your design decisions.
ask
Ask Gemini (via agy) a question, optionally with file context.
rescue
Delegate investigation, an explicit fix request, or follow-up rescue work to the Gemini rescue subagent.
review
Run a Gemini code review against local git state.