unschedule-playbook

A command for cancelling a scheduled playbook routine. A playbook is a saved sequence of browser actions or checks.

In plain words
What is it for?
Use it to find and delete the scheduled routine associated with a named playbook.
Why use it?
It removes an unwanted recurring run and reports when no matching scheduled routine exists.

Command

Install

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.

agentmods
npx agentmods add commands/devzonayed/mochi/unschedule-playbook
Clone the repo
git clone --depth 1 https://github.com/DevZonayed/Mochi
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 101 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00007 $0.00101
Opus 5 $0.00003 $0.00051
Sonnet 5 $0.00001 $0.00020
Haiku 4.5 $0.00001 $0.00010

Measured 2d ago against content hash a6d8d7fb6ff2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

plugins/qa/commands/unschedule-playbook.md · 11 lines

What it actually says

Cancel the scheduled routine for playbook $ARGUMENTS.

  1. Use the schedule skill (if available) to find the routine that runs this playbook (typically named mochi-playbook:$ARGUMENTS) and delete it.
  2. If no such routine exists, report: "no scheduled routine found for $ARGUMENTS."
Changes

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.

  1. 2d ago First seen · 11 lines · 7 tokens per session scan A a6d8d7fb6ff2

Subscribe to this mod's changes

unschedule-playbook is a command published in the GitHub repository DevZonayed/Mochi (3 stars, last pushed 16d ago), licensed MIT. It adds 7 tokens to every session and 101 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.