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/recallgit 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.00015 | $0.00157 |
| Opus 5 | $0.00008 | $0.00078 |
| Sonnet 5 | $0.00003 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
recall 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
Run the recall helper and show its output to the user verbatim:
node "$(cat .continuum/.plugin-root)/lib/recall_cli.js" -- $ARGUMENTS
After showing the output:
- If a hit's
_anchors:_line references a commit, the user may want detail from that commit — offer togit show <sha>. - If a hit references an archived transcript span (
archive_pathin refs), offer tozcatand surface the relevant lines. - Do NOT re-summarize what's already in the output unless the user asks.
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 · 17 lines · 15 tokens per session scan A 65b95f6492c2
recall is a command published in the GitHub repository DevZonayed/Mochi (3 stars, last pushed 15d ago), licensed MIT. It adds 15 tokens to every session and 157 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'.