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/mirage20/ccstatus-go/commitgit clone --depth 1 https://github.com/Mirage20/ccstatus-goWhat 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.00007 | $0.00186 |
| Opus 5 | $0.00003 | $0.00093 |
| Sonnet 5 | $0.00001 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
commit 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.
What it actually says
Context
- Current git status: !
git status --short - Staged changes: !
git diff --cached - Current branch: !
git branch --show-current - Recent commits: !
git log --oneline -5
Task
Create a single git commit with the staged changes.
$ARGUMENTS
If a commit message was provided above, use it. Otherwise, generate an appropriate message that:
- Summarizes what changed
- Follows the repository's commit format
- Is clear and concise
Important Notes
- Only commit staged changes
- If no changes are staged, suggest using
git addfirst - Verify the commit was created successfully
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 · 30 lines · 7 tokens per session scan A 21906136061a
commit is a command published in the GitHub repository Mirage20/ccstatus-go (11 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 186 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
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).
autospec.plan
Generate YAML implementation plan from feature specification.
version
Show installed vs latest ai-sdlc plugin version. Bypasses the 24h SessionStart cache.
release-tag
Create and push a version tag after a release PR has been merged.
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
fix
Auto-fix linting, formatting, and common issues.