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/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.00024 | $0.00250 |
| Opus 5 | $0.00012 | $0.00125 |
| Sonnet 5 | $0.00005 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
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 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.
What it actually says
!bash "${CLAUDE_PLUGIN_ROOT}/scripts/cli-dispatch-status.sh" "${CLAUDE_PLUGIN_ROOT}"
The status report above already ran — do NOT run it again.
Present it to the user as-is, grouped by the == backend headings. Keep it compact;
add no prose beyond what the report says. The report never prints a key VALUE, only
whether one is set — keep it that way.
If everything is in place, suggest an optional smoke test (as a background task):
claude-ds -p "Reply with exactly: OK".
Native Windows only — if the block above failed because bash is unavailable,
run the PowerShell twin instead (it covers DeepSeek and Codex; the Antigravity,
OpenCode and Copilot backends are Unix-only):
powershell -NoProfile -ExecutionPolicy Bypass -File "$env:CLAUDE_PLUGIN_ROOT/scripts/cli-dispatch-status.ps1" -PluginRoot "$env:CLAUDE_PLUGIN_ROOT"
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 · 24 lines · 24 tokens per session scan A d6a55a407842
status is a command published in the GitHub repository rbinar/cli-dispatch (5 stars, last pushed 14d ago), licensed MIT. It adds 24 tokens to every session and 250 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-31.
Other commands, from other repositories
rebase
Rebase current branch onto trunk (origin/master or origin/main), predict and resolve conflicts.
execute
Enter EXECUTE mode to implement approved plan.
innovate
Enter INNOVATE mode for brainstorming approaches.
research
Enter RESEARCH mode for information gathering.
verify
Adversarial spec-vs-implementation verification for a completed task. Dispatches the spec-mentor subagent with fresh context (no anchoring bias), parses its verdict (PASS / DRIFT / NEEDS-MARTY), and updates the verification queue. The v7.4.0 architectural replacement for a dedicated "mentor session.".
criar-skill
Use when creating new skills, automations, or specialized knowledge packages. Keywords: criar skill, nova skill, automatizar, conhecimento, TDD skill.