Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ma-ziwei/fathom-mode-for-claude/plugin install fathomWrote 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/ma-ziwei/fathom-mode-for-claude/plan)<a href="https://agentmods.dev/commands/ma-ziwei/fathom-mode-for-claude/plan"><img src="https://agentmods.dev/badge/commands/ma-ziwei/fathom-mode-for-claude/plan/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/ma-ziwei/fathom-mode-for-claude/plan"><img src="https://agentmods.dev/badge/commands/ma-ziwei/fathom-mode-for-claude/plan.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.00015 | $0.00216 |
| Opus 5 | $0.00008 | $0.00108 |
| Sonnet 5 | $0.00003 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
plan 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 9d 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
Run via Bash:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/compile_plan.py
Read its stdout as the structured intent markdown — do NOT show this to the user verbatim. Write a plan for the user's task, grounded in every section of the structured intent. Do not introduce concerns absent from the intent. Honor every constraint listed.
Present the plan and end with:
Reply approve to proceed with this plan, reject to discard, or describe what to change.
(From here the hook's AWAITING_APPROVAL reminder takes over and manages the approve / reject / change flow on subsequent turns. This slash command exists for users who prefer an explicit slash entry; the conversational "plan" trigger from the IN_SESSION hook reminder produces the same state transition via the same compile_plan.py invocation, since compile_plan.py itself sets state.awaiting_approval = True regardless of entry path.)
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.
- 9d ago First seen · 19 lines · 15 tokens per session scan A a405cac2ce98
plan is a command published in the GitHub repository ma-ziwei/fathom-mode-for-claude (13 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 216 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-30.
Other commands, from other repositories
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
sdd
Generate a Kiro-style spec triple — specs/ /{requirements,design,tasks}.md.
drive
Drive a goal to completion over the deterministic firewall — the autonomous goal-driven loop.
brief
Turn a raw request plus attached documents into a validated one-page brief under briefs/ /.
plan
Create a detailed work plan with DoD and save it in memory-bank.
config
Manage execution pipeline.yaml — init / show / validate / path.