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/devzonayed/mochi/schedule-playbookgit clone --depth 1 https://github.com/DevZonayed/MochiWhat 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.00020 | $0.00258 |
| Opus 5 | $0.00010 | $0.00129 |
| Sonnet 5 | $0.00004 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
schedule-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.
What it actually says
The user wants to schedule playbook $ARGUMENTS for recurring execution.
- Call
browser_playbook_getfor the id. Ifmeta.cronis absent or empty, report: "playbook$ARGUMENTShas nocron:field. Edit the playbook frontmatter to set one (e.g.,cron: '0 7 * * 1-5'for weekdays at 7am)." - Otherwise, invoke the
scheduleskill (if available in this environment) to register a routine that runsbrowser_playbook_run { id: "$ARGUMENTS", inputs: <playbook.schedule_inputs> }on the given cron schedule. The routine output should be appended to.continuum/playbooks/inbox/<schedule_inbox or default>/<runId>.md. - If the
scheduleskill is not available in this environment, report: "scheduling unavailable in this env; please run the playbook manually via/mochi:playbook run $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.
- 2d ago First seen · 12 lines · 20 tokens per session scan A 9f763cf0ea62
schedule-playbook is a command published in the GitHub repository DevZonayed/Mochi (3 stars, last pushed 16d ago), licensed MIT. It adds 20 tokens to every session and 258 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
toon
A lightweight data format designed to minimize token usage when passing structured data to LLMs.
browse
You have access to a browser via the MCP Browser Bridge tools. Use them to interact with web pages.
computer
Control the macOS desktop — move mouse, click, type, press keys, scroll, drag, take screenshots, list windows/displays, clipboard. Uses usecomputer CLI for native Quartz event automation.
autoresearch
Autonomous research loop — iteratively edit, test, measure, keep/discard. Usage: /autoresearch [--budget 5m] [--provider ark].
gitlab-scrum
GitLab Scrum management - create/manage issues, labels, milestones, and boards. Use when user says: create issue, list issues, move issue, add label, scrum, kanban, backlog, or task tracking.
web-setup
Guide users through Chrome extension setup for browser control. Use when user asks about setup, installing the extension, connecting Chrome, or when browsercontrol tools return 'No browser connected'.