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/clean-schedulegit 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.00017 | $0.00865 |
| Opus 5 | $0.00009 | $0.00432 |
| Sonnet 5 | $0.00003 | $0.00173 |
| Haiku 4.5 | $0.00002 | $0.00086 |
Grade A, and why
clean-schedule 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
!bash "${CLAUDE_PLUGIN_ROOT}/scripts/cli-dispatch-clean-schedule.sh" status
The block above is the current schedule state only — it was pre-executed as a
read-only status probe. It did NOT install or remove anything, whatever
$ARGUMENTS says.
cli-dispatch clean-schedule
Registers a daily, OS-level auto-clean that runs cli-dispatch-clean --remove
in the background, so stale worker dirs (a running session whose process died
before finalize) are pruned even when Claude Code isn't open. launchd on macOS,
cron on Linux/WSL. No cloud agent, no tokens. It only ever removes stale dirs
(idle > 600 s while running); a live worker is never touched. The job logs to
~/.cache/cli-dispatch/clean.log.
What to do now
Read the action out of $ARGUMENTS: install (the command's default when no
action is given) | status | uninstall, plus optional --time HH:MM (default
03:00) and --older-than DAYS (also prune old finished sessions; default off →
stale only).
-
Action is
status— you already have the answer above. Report it and stop. -
Action is
installoruninstall— this mutates the OS scheduler, so run it as a deliberate step, forwarding the user's arguments verbatim:bash "${CLAUDE_PLUGIN_ROOT}/scripts/cli-dispatch-clean-schedule.sh" $ARGUMENTSIf
$ARGUMENTScarries no action word, passinstallexplicitly — the script's own default isstatusprecisely so that a bare run can never write a plist or rewrite a crontab.
Prereq: cli-dispatch-clean on PATH (it is, via /cli-dispatch:setup). After an
install, confirm with the same command + status. To stop it: ... uninstall.
Native Windows only (Scheduled Tasks)
The bash script covers macOS and Linux/WSL. On native Windows use this instead:
$parts = "$env:ARGUMENTS".Trim() -split '\s+'
$action = 'install'; $time = '03:00'; $older = ''
for ($i = 0; $i -lt $parts.Count; $i++) { switch ($parts[$i]) {
{ $_ -in 'install','status','uninstall' } { $action = $_ }
'--time' { $time = $parts[++$i] }
'--older-than' { $older = $parts[++$i] } } }
$name = 'cli-dispatch-clean'
$bin = (Get-Command cli-dispatch-clean.cmd -ErrorAction SilentlyContinue).Source
if (-not $bin) { $bin = Join-Path $HOME '.local/bin/cli-dispatch-clean.cmd' }
$argline = '--remove --quiet'; if ($older) { $argline += " --older-than $older" }
switch ($action) {
'status' { schtasks /Query /TN $name /V /FO LIST 2>$null; if ($LASTEXITCODE -ne 0) { 'not scheduled.' } }
'uninstall' { schtasks /Delete /TN $name /F 2>$null; 'removed schedule.' }
'install' {
schtasks /Create /TN $name /TR "`"$bin`" $argline" /SC DAILY /ST $time /F | Out-Null
"scheduled daily at $time (Scheduled Task: $name)."
}
}
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 · 68 lines · 17 tokens per session scan A 1e8f2dd7c2bf
clean-schedule is a command published in the GitHub repository rbinar/cli-dispatch (5 stars, last pushed 14d ago), licensed MIT. It adds 17 tokens to every session and 865 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.