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/rbinar/cli-dispatch/cx-statusgit clone --depth 1 https://github.com/rbinar/cli-dispatchWhat 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.00014 | $0.00142 |
| Opus 5 | $0.00007 | $0.00071 |
| Sonnet 5 | $0.00003 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
cx-status 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.
This is a copy
83% identical to cp-status — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
!bash "${CLAUDE_PLUGIN_ROOT}/scripts/cli-dispatch-status.sh" --backend codex "${CLAUDE_PLUGIN_ROOT}"
The Codex status report above already ran — do NOT run it again. Present it
as-is and keep it compact. The report never prints a key VALUE, only whether
one is set — keep it that way. For all backends use /cli-dispatch:status.
If everything is in place, suggest an optional smoke test (background task):
cx-agent --read-only -q "Reply with exactly: OK".
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 · 14 lines · 14 tokens per session scan A 0e49689ee260
cx-status is a command published in the GitHub repository rbinar/cli-dispatch (5 stars, last pushed 14d ago), licensed MIT. It adds 14 tokens to every session and 142 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to cp-status, differing in 12 lines, and is treated as a copy.
Other commands, from other repositories
strict
Enable strict RIPER protocol enforcement.
research
Enter RESEARCH mode for information gathering.
status
Show the current status of the Claude Code Router server.
brainstorm
多模型并行对同一问题各给独立意见(发散式 brainstorming),主 Claude 综合分歧、共识、独到见解。各模型彼此看不到对方答案,避免回声室效应。.
language
Toggle the HUD label language between English and 中文 (edits /.claude/plugins/balance-hud/config.json).
benchmark
Run the Permafrost cache benchmark (offline emulator, no API key).