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 waazy-w/claude-phantom/plugin install phantomWrote 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/waazy-w/claude-phantom/recover)<a href="https://agentmods.dev/commands/waazy-w/claude-phantom/recover"><img src="https://agentmods.dev/badge/commands/waazy-w/claude-phantom/recover/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/waazy-w/claude-phantom/recover"><img src="https://agentmods.dev/badge/commands/waazy-w/claude-phantom/recover.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.00032 | $0.00813 |
| Opus 5 | $0.00016 | $0.00407 |
| Sonnet 5 | $0.00006 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
recover 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.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recover from a crash using the crash-recovery skill. You are running interactively, so you own the git branch setup that phantom's CLI would otherwise handle.
Input
$ARGUMENTS
- If the argument is a path ending in
.json, read it: it is a phantomCrashContext(command, exit summary, errorLine, stackTrace, hintFiles, tail, git, pkg, testCommand). - If the argument is empty, find the newest file in
.phantom/crashes/(ls -t .phantom/crashes/*.json | head -1) and read it. If there is none, ask the user to paste the error or run the crashing command. - Otherwise treat the argument as pasted error output: extract the error line, stack trace, and file paths yourself.
Setup (interactive only)
- Run
git status --porcelain. If the tree is dirty, stop and ask the user to commit or stash first (never stash for them). - Record the base:
git rev-parse --abbrev-ref HEADandgit rev-parse HEAD. - Derive a slug from the error line (lowercase,
a-z0-9-, at most 48 chars) and create the branch:git checkout -b phantom/fix-<slug>. This is the ONE git mutation you may perform in this command; it is forbidden inside the skill's phases. - Determine the test command:
.phantomrctestCommand, elsepackage.jsonscripts.test(npm test), elsenode --test test/*.test.js. - Never-touch paths:
.env,.env.*,**/*.pem,**/*.key,**/secrets/**,**/*.secret*,.git/**,node_modules/**, plus anyneverTouchin.phantomrc.
Procedure
Follow the crash-recovery skill phases 0 through 5 exactly, with at most 3 verification attempts. Write the report to .phantom/reports/<YYYYMMDD-HHmmss>-<slug>.md using the template at ${CLAUDE_PLUGIN_ROOT}/templates/post-mortem.md, which ships with this plugin. If it cannot be read, fall back to templates/post-mortem.md in the repo, and only then to the same section order from memory.
Finish
- Show
git diff --statand the report path. - Ask the user whether to commit on the phantom branch (
git add -A && git commit -m "phantom: fix <error>"). Do not commit without a yes. - Remind them how to review:
git diff <base>..phantom/fix-<slug>,git merge, orgit branch -Dto discard. Do not switch branches back yourself; the user decides.
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 · 34 lines · 32 tokens per session scan A d60bf34bb706
recover is a command published in the GitHub repository waazy-w/claude-phantom (4 stars, last pushed 17d ago), licensed MIT. It adds 32 tokens to every session and 813 once invoked, about $0.0002 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
map
Generate MAP.md — a relational map of every file, function, signature, and call in the repo.
audit-release
Diagnose release-readiness against the Starter Series quality bar — matched starter, version-vs-last-tag drift, CHANGELOG drift vs merged PRs, and publish-workflow kind. Read-only.
sanity
Cross-check a dekko callers/uses result against a targeted grep before trusting a low/zero count.
doctor
Diagnose dekko environment/install issues (PATH shadowing, map freshness, MCP registration, plugin, hooks, CLAUDE.md policy block).
bug-plan-creator
Deep bug investigation with architectural fix plan generation - works with any executor (loop or swarm).
agy-debug
Send an error/stack trace plus the relevant file(s) to Antigravity (agy) for root-cause analysis.