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/restoregit 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/restore)<a href="https://agentmods.dev/commands/sofumel/claude-handoff-revive/restore"><img src="https://agentmods.dev/badge/commands/sofumel/claude-handoff-revive/restore.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 | $0.00032 | $0.00311 |
| Opus 5 | $0.00016 | $0.00156 |
| Sonnet 5 | $0.00006 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
restore 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 4d 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
Restore the snapshot the user named ($ARGUMENTS). If no timestamp was given, run /handoff-revive:list behavior first (list-history script) and ask which one to restore.
- Linux/macOS/WSL/Git-Bash:
bash "${CLAUDE_PLUGIN_ROOT:-.claude}/skills/handoff-revive/scripts/restore-history.sh" <timestamp> - Windows PowerShell:
$r = if ($env:CLAUDE_PLUGIN_ROOT) { $env:CLAUDE_PLUGIN_ROOT } else { ".claude" }; powershell -ExecutionPolicy Bypass -File "$r/skills/handoff-revive/scripts/restore-history.ps1" -Timestamp <timestamp>
The script archives the existing current.md into history before overwriting, so nothing is lost. On success, confirm in the user's language and offer to run /handoff-revive:resume to continue from the restored snapshot.
Note: this restores the structured handoff snapshot (goal / done / wip / todo / next_action / touched_files / decisions / lessons_learned) — not the full conversation. Rolling back conversation history is what native --resume / /rewind do; this restores the much cheaper work-state checkpoint instead.
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.
- 4d ago First seen · 20 lines · 32 tokens per session scan A 10f03d0519a9
restore is a command published in the GitHub repository sofumel/claude-handoff-revive (6 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 311 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
quick
Glance do projeto em 30-60 segundos. Stack detection, top simbolos, atividade git, convencoes basicas. Versao leve do init - serve como primeira impressao antes de rodar analise completa.
in-flight
Mostra branches e PRs ativos no repositório. Use antes de planejar para evitar duplicação ou conflito com trabalho em andamento.
owner
Mostra quem domina determinado arquivo ou pasta, baseado em git history. Inclui top contributor, % de autoria, co-autores notáveis.
triage
Move tracker issues and external PRs through the triage state machine into agent-ready briefs. Use when triaging incoming issues, an external PR, or the backlog. Reads the tracker + label config written by /orc:setup.
jira-breakdown
Turn a feature brief, PRD, or existing Epic into a full Jira hierarchy behind a preview gate. Use when building out a Jira epic/backlog, breaking a feature into Jira tickets, or enforcing the Epic→Story→Task structure.
resolve-todos
Resolve approved TODOs in parallel using worker agents — one agent per TODO.