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/sofumel/claude-handoff-revive/doctorgit clone --depth 1 https://github.com/sofumel/claude-handoff-reviveWrote 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/sofumel/claude-handoff-revive/doctor)<a href="https://agentmods.dev/commands/sofumel/claude-handoff-revive/doctor"><img src="https://agentmods.dev/badge/commands/sofumel/claude-handoff-revive/doctor.svg" alt="Measured on agentmods" 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.00023 | $0.00237 |
| Opus 5 | $0.00012 | $0.00118 |
| Sonnet 5 | $0.00005 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
doctor 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 5d 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 the doctor-handoff script and present the result in the user's language (read .claude/handoff/lang if present):
- Linux/macOS/WSL/Git-Bash:
bash "${CLAUDE_PLUGIN_ROOT:-.claude}/skills/handoff-revive/scripts/doctor-handoff.sh" - Windows PowerShell:
$r = if ($env:CLAUDE_PLUGIN_ROOT) { $env:CLAUDE_PLUGIN_ROOT } else { ".claude" }; powershell -ExecutionPolicy Bypass -File "$r/skills/handoff-revive/scripts/doctor-handoff.ps1"
Show the PASS/WARN/INFO lines as-is, then summarize: if there are WARN lines, explain in 1–2 sentences what each one means and the most likely fix (HOOK_SETUP.md for hook wiring, reinstall for missing script pairs, /handoff-revive:save then validate for an invalid handoff). If everything passes, say the installation looks healthy.
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.
- 5d ago First seen · 17 lines · 23 tokens per session scan A 50caea1b4e35
doctor is a command published in the GitHub repository sofumel/claude-handoff-revive (6 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 237 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
recall
Recover context from recent conversation.
remember
Save the current session to persistent context memory.
recall
Search past sessions stored in context memory.
sync
Manually trigger plan-sync to update downstream task specs after implementation drift.
vitaecontext-github
Audit or improve GitHub profile and repository SEO.
vitaecontext-vitaegraph
Create, validate, index, or use a private VitaeGraph.