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/gaingit 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.00006 | $0.00239 |
| Opus 5 | $0.00003 | $0.00120 |
| Sonnet 5 | $0.00001 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
gain 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
cli-dispatch gain
Read-only token accounting summary over worker session status.json files,
plus Anthropic babysitting token usage from legacy runner-subagent transcripts on this
machine (a subagent counted as a runner when it actually invoked a wrapper CLI —
ds-agent, cx-stream, etc. — in a Bash tool call; other subagents are
summarized in one line and excluded from the ratio). The five per-backend runner
subagents (ds-/ag-/cx-/oc-/cp-runner) have since been retired — measured babysitting
overhead ran ~906% of worker output — in favor of the deterministic runner
(/cli-dispatch:run, zero LLM babysitter tokens); this report's babysitter/worker ratio
reflects historical sessions from before that change.
if command -v cli-dispatch-gain >/dev/null 2>&1; then
cli-dispatch-gain "$@"
else
node "${CLAUDE_PLUGIN_ROOT}/scripts/gain-report.mjs" "$@"
fi
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 · 25 lines · 6 tokens per session scan A 845e9bb8a165
gain is a command published in the GitHub repository rbinar/cli-dispatch (5 stars, last pushed 13d ago), licensed MIT. It adds 6 tokens to every session and 239 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-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.