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/spec-initgit 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.00010 | $0.00616 |
| Opus 5 | $0.00005 | $0.00308 |
| Sonnet 5 | $0.00002 | $0.00123 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
spec-init 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Initialization
Initialize a new specification based on the provided project description:
Project Description: $ARGUMENTS
Task: Initialize Specification Structure
SCOPE: This command initializes the directory structure and metadata based on the detailed project description provided.
1. Generate Feature Name
Create a concise, descriptive feature name from the project description ($ARGUMENTS).
Check existing .kiro/specs/ directory to ensure the generated feature name is unique. If a conflict exists, append a number suffix (e.g., feature-name-2).
2. Create Spec Directory
Create .kiro/specs/[generated-feature-name]/ directory with:
spec.json- Metadata and approval trackingrequirements.md- Lightweight template with project description
Note: design.md and tasks.md will be created by their respective commands during the development process.
3. Initialize spec.json Metadata
Create initial metadata with approval tracking:
{
"feature_name": "[generated-feature-name]",
"created_at": "current_timestamp",
"updated_at": "current_timestamp",
"language": "en",
"phase": "initialized",
"approvals": {
"requirements": {
"generated": false,
"approved": false
},
"design": {
"generated": false,
"approved": false
},
"tasks": {
"generated": false,
"approved": false
}
},
"ready_for_implementation": false
}
4. Create Requirements Template
Create requirements.md with project description:
# Requirements Document
## Project Description (Input)
$ARGUMENTS
## Requirements
<!-- Will be generated in /kiro:spec-requirements phase -->
5. Update CLAUDE.md Reference
Add the new spec to the active specifications list with the generated feature name and a brief description.
Next Steps After Initialization
Follow the strict spec-driven development workflow:
/kiro:spec-requirements <feature-name>- Create and generate requirements.md/kiro:spec-design <feature-name>- Create and generate design.md (requires approved requirements)/kiro:spec-tasks <feature-name>- Create and generate tasks.md (requires approved design)
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 · 86 lines · 10 tokens per session scan A f520df2500df
spec-init is a command published in the GitHub repository kbwo/ccmanager (1,229 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 616 once invoked, about $0.0001 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.