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/status)<a href="https://agentmods.dev/commands/ma-ziwei/fathom-mode-for-claude/status"><img src="https://agentmods.dev/badge/commands/ma-ziwei/fathom-mode-for-claude/status/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/status"><img src="https://agentmods.dev/badge/commands/ma-ziwei/fathom-mode-for-claude/status.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.00014 | $0.00176 |
| Opus 5 | $0.00007 | $0.00088 |
| Sonnet 5 | $0.00003 | $0.00035 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
status 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
Show the current state of the active Fathom session.
Steps:
-
Run
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/render_status.pyvia Bash. It returns a markdown-formatted summary of the graph and score. -
Present the script's output verbatim — do not rewrite, summarize, or reorder. The user is asking to inspect the white-box state.
-
After the rendered status, remind the user briefly of next-step commands:
/fathom:plan— plan from the session/fathom:exit— leave the session
If render_status.py exits with a non-zero status (e.g. no active session), present its error message verbatim and stop.
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 · 14 tokens per session scan A 55cfabb3604a
status is a command published in the GitHub repository ma-ziwei/fathom-mode-for-claude (13 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 176 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.
plan
Create a detailed work plan with DoD and save it in memory-bank.
brief
Turn a raw request plus attached documents into a validated one-page brief under briefs/ /.
done
End session — actualize core MB files, create a note, append to progress.