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/switchgit clone --depth 1 https://github.com/sofumel/claude-handoff-reviveWhat 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.00021 | $0.00295 |
| Opus 5 | $0.00010 | $0.00148 |
| Sonnet 5 | $0.00004 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
switch 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 2d 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 switch-branch-handoff script and relay its output in the user's language (read .claude/handoff/lang):
- Linux/macOS/WSL/Git-Bash:
bash "${CLAUDE_PLUGIN_ROOT:-.claude}/skills/handoff-revive/scripts/switch-branch-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/switch-branch-handoff.ps1"
What it does: current.md stays the single active handoff; the one belonging to another branch is parked under .claude/handoff/branches/<branch>.md and the current branch's parked handoff (if any) is restored. Nothing is destroyed — collisions are archived to history first.
After a successful restore, offer /handoff-revive:resume. If it restored nothing (clean slate), suggest /handoff-revive:save once work starts. If it errors because the handoff has no branch: metadata, explain it predates v1.1 and should be re-saved on its own branch first.
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.
- 2d ago First seen · 19 lines · 21 tokens per session scan A 6b4974f6d530
switch is a command published in the GitHub repository sofumel/claude-handoff-revive (6 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 295 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.
execute
Executa o plano aprovado em .first-plan/07-state/plans/. Segue o plano à risca, para se algo invalidar premissa, gera relatório ao final.
setup
Set up Postman MCP Server. Authenticate via OAuth or API key, verify connection, select workspace.
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.