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/steeringgit 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.00012 | $0.02076 |
| Opus 5 | $0.00006 | $0.01038 |
| Sonnet 5 | $0.00002 | $0.00415 |
| Haiku 4.5 | $0.00001 | $0.00208 |
Grade A, and why
steering 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 2d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kiro Steering Management
Intelligently create or update steering documents in .kiro/steering/ to maintain accurate project knowledge for spec-driven development. This command detects existing documents and handles them appropriately.
Existing Files Check
Current steering documents status
- Product overview: !
bash -c '[ -f ".kiro/steering/product.md" ] && echo "✅ EXISTS - Will be updated preserving custom content" || echo "📝 Not found - Will be created"' - Technology stack: !
bash -c '[ -f ".kiro/steering/tech.md" ] && echo "✅ EXISTS - Will be updated preserving custom content" || echo "📝 Not found - Will be created"' - Project structure: !
bash -c '[ -f ".kiro/steering/structure.md" ] && echo "✅ EXISTS - Will be updated preserving custom content" || echo "📝 Not found - Will be created"' - Custom steering files: !
bash -c 'ls .kiro/steering/*.md 2>/dev/null | grep -v -E "(product|tech|structure).md" | wc -l'
Project Analysis
Current Project State
- Project files: !
bash -c 'find . -path ./node_modules -prune -o -path ./.git -prune -o -path ./dist -prune -o -type f \( -name "*.py" -o -name "*.js" -o -name "*.ts" -o -name "*.jsx" -o -name "*.tsx" -o -name "*.java" -o -name "*.go" -o -name "*.rs" \) -print 2>/dev/null || echo "No source files found"' - Configuration files: !
bash -c 'find . -maxdepth 3 \( -name "package.json" -o -name "requirements.txt" -o -name "pom.xml" -o -name "Cargo.toml" -o -name "go.mod" -o -name "pyproject.toml" -o -name "tsconfig.json" \) 2>/dev/null || echo "No config files found"' - Documentation: !
bash -c 'find . -maxdepth 3 -path ./node_modules -prune -o -path ./.git -prune -o -path ./.kiro -prune -o \( -name "README*" -o -name "CHANGELOG*" -o -name "LICENSE*" -o -name "*.md" \) -print 2>/dev/null || echo "No documentation files found"'
Recent Changes (if updating)
- Last steering update: !
bash -c 'git log -1 --oneline -- .kiro/steering/ 2>/dev/null || echo "No previous steering commits"' - Commits since last steering update: !
bash -c 'LAST_COMMIT=$(git log -1 --format=%H -- .kiro/steering/ 2>/dev/null); if [ -n "$LAST_COMMIT" ]; then git log --oneline ${LAST_COMMIT}..HEAD --max-count=20 2>/dev/null || echo "Not a git repository"; else echo "No previous steering update found"; fi' - Working tree status: !
bash -c 'git status --porcelain 2>/dev/null || echo "Not a git repository"'
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.
- 2d ago First seen · 172 lines · 12 tokens per session scan A 22bdf1b90225
steering is a command published in the GitHub repository kbwo/ccmanager (1,229 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 2,076 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.