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.
git clone --depth 1 https://github.com/DevZonayed/MochiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/devzonayed/mochi/unschedule-playbook)<a href="https://agentmods.dev/commands/devzonayed/mochi/unschedule-playbook"><img src="https://agentmods.dev/badge/commands/devzonayed/mochi/unschedule-playbook/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/devzonayed/mochi/unschedule-playbook"><img src="https://agentmods.dev/badge/commands/devzonayed/mochi/unschedule-playbook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00007 | $0.00101 |
| Opus 5.5 | $0.00003 | $0.00040 |
| Sonnet 5.5 | $0.00001 | $0.00020 |
| Haiku 4.5 | $0.00001 | $0.00010 |
Grade A, and why
unschedule-playbook 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 1mo 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.
What it actually says
Cancel the scheduled routine for playbook $ARGUMENTS.
- Use the
scheduleskill (if available) to find the routine that runs this playbook (typically namedmochi-playbook:$ARGUMENTS) and delete it. - If no such routine exists, report: "no scheduled routine found for
$ARGUMENTS."
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.
- 1mo ago First seen · 11 lines · 7 tokens per session scan A a6d8d7fb6ff2
unschedule-playbook is a command published in the GitHub repository DevZonayed/Mochi (3 stars, last pushed 2d ago), licensed MIT. It adds 7 tokens to every session and 101 once invoked, about $0.0000 per session on Opus 5.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
intercept
HTTP sniffer for tandem's Chrome via CDP: captures request+response bodies (including HttpOnly, CSRF tokens, private APIs). Subcommands: start, show, clear, count.
Captures the current page in tandem's Chrome as a PDF (if headless Chrome) or full-page PNG screenshot (in normal tandem mode). Saves to /.claude/tandem/output/.
cookies
Exports cookies from tandem's Chrome via CDP (includes HttpOnly/Secure). Filter with --domain . Formats: list (table, default), json, curl, headers, netscape.
browser-start
../../../commands/browser-start.md.
browser-status
../../../commands/browser-status.md.
browser-stop
../../../commands/browser-stop.md.