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/ds-rungit 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.00012 | $0.00728 |
| Opus 5 | $0.00006 | $0.00364 |
| Sonnet 5 | $0.00002 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
ds-run 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
Delegate a task to claude-ds
Task to delegate: $ARGUMENTS
The task runs via claude-ds-stream: its output is parsed as stream-json and written to a
session directory → live, observable, resumable. Monitor progress in a cost-conscious way:
read only the small status.json, never the raw transcript.
If it's a real repo task (file changes needed) — use an isolated worktree:
-
Write the task to a brief file (e.g.
/tmp/ds-brief.txt). -
Run it (as a background task) — macOS / Linux / WSL / Git Bash:
"${CLAUDE_PLUGIN_ROOT}/scripts/ds-worktree-run.sh" <repo-path> <branch-name> /tmp/ds-brief.txt(The script uses
claude-ds-streaminternally; the session directory is printed on stderr.)Windows: repo tasks need bash (WSL or Git Bash). The PowerShell twin of this runner was removed in 4.6.0 (issue #125) — nothing selected it,
cli-dispatch-run.ps1requires bash for worktree runs anyway, and a second uncalled copy of the guard logic could only drift. Pure generation (below) and every other Windows path are unaffected. -
Monitor (cost-conscious): capture the session id, occasionally check
status.jsonvia/cli-dispatch:watch <id>(state: running→done). Do NOT tight-loop tail. -
When done, review the diff in the worktree (
git -C <worktree> diff), verify independently (tsc/build/test). -
If all good, you handle git/commit/push/PR/merge; then clean up the worktree.
If it's pure generation (code/text, no files) — as a background task:
claude-ds-stream -p "$ARGUMENTS"
The final text is printed to stdout; progress lives in status.json/progress.log. Session id on stderr.
Note: the worker runs with bypassPermissions, so it can still write files even here. If the output must be text-only with no disk writes, add
--read-only(claude-ds-stream --read-only -p "$ARGUMENTS") — it denies Write/Edit/Bash.
Reasoning effort:
ds-agent --effort high -q "$ARGUMENTS"
--effort low|medium|high maps to a thinking-token budget via MAX_THINKING_TOKENS
(low=1024, medium=8192, high=31999), applied through the CLI wrapper's --effort flag.
Best-effort — only honored if the DeepSeek Anthropic-compatible API respects the thinking budget.
Follow-up / fix (continue the same DeepSeek session):
claude-ds-stream --resume <session-id> -p "<follow-up>"
To see all sessions, use /cli-dispatch:sessions.
claude-ds = worker, you = reviewer/merge owner. Don't trust the output until verified.
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 · 58 lines · 12 tokens per session scan A cd802c7df034
ds-run is a command published in the GitHub repository rbinar/cli-dispatch (5 stars, last pushed 13d ago), licensed MIT. It adds 12 tokens to every session and 728 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.