CCManager is a command-line application for managing multiple sessions of AI coding assistants across Git worktrees and projects. It is for developers working with tools such as Claude Code, Gemini CLI, Codex CLI, Cursor Agent, Copilot CLI, Cline CLI, OpenCode, and Kimi CLI, and the catalogue entries provide commands and instructions for its workflows.
Borrowing it
Nothing to install: this file belongs to kbwo/ccmanager. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kbwo/ccmanager/main/.claude/commands/kiro/validate-gap.mdgit clone --depth 1 https://github.com/kbwo/ccmanagerWrote 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/kbwo/ccmanager/validate-gap)<a href="https://agentmods.dev/commands/kbwo/ccmanager/validate-gap"><img src="https://agentmods.dev/badge/commands/kbwo/ccmanager/validate-gap/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/kbwo/ccmanager/validate-gap"><img src="https://agentmods.dev/badge/commands/kbwo/ccmanager/validate-gap.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00009 | $0.01253 |
| Opus 5.5 | $0.00004 | $0.00501 |
| Sonnet 5.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 1mo 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 — 91% identical, 7 lines differ
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.
- 1mo ago First seen · 156 lines · 9 tokens per session scan A 9adbb60ada11
validate-gap is a command published in the GitHub repository kbwo/ccmanager (1,264 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 1,253 once invoked, about $0.0000 per session on Opus 5.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
maestro-odyssey
Long-running iterative cycle — one entry, seven modes (debug|improve|planex|review|security|defensive|ui). Shared archaeology/audit → fix → verify → generalize → discover → persist skeleton with mode-specific dimensions. User-invoked campaign entry; single-step fixes route via /maestro-next.
fix
PURPOSE: Fix issues in based on feedback TASK.
fix
Diagnose and fix bugs, errors, and issues in code.
agy-debug
Send an error/stack trace plus the relevant file(s) to Antigravity (agy) for root-cause analysis.
doctor
Diagnose a broken llm-router setup.
debug-files
Command "debug-files" from getsentry/toolkit, covering examples, inspect a debug information file (auto-detects the format), bundle jvm sources with a debug id, exclude additional directories and output as json.