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 sofumel/claude-handoff-revive/plugin install 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/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/sofumel/claude-handoff-revive/restore"><img src="https://agentmods.dev/badge/commands/sofumel/claude-handoff-revive/restore.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.00311 |
| Opus 5.5 | $0.00013 | $0.00124 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (8 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 311 once invoked, about $0.0001 per session on Opus 5.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
flow
Conductor - an idea or change request, a spec or task id, a tracker issue, a branch or path, a bug report, a how or why question, something slow, a behaviour-keeping cleanup, a design fork, or "what next"; --auto drives a ready spec unattended (--tick for one hop) and ends with a PILOTVERDICT line; --until=merge…
tracker-sync
Project a flow spec to a tracker (Linear/GitHub/GitLab/Jira) and reconcile body/status/comments two-way — projection, not coordination. NOT plan-sync (/flow-next:sync).
audit
Audit .flow/memory/ entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry.
features
Seed or maintain the committed user-POV feature map at .flow/features/.
make-pr
Render a cognitive-aid PR body from flow-next state and open via gh.
strategy
Create or maintain STRATEGY.md — repo-root anchor for target problem, approach, users, key metrics, and tracks.