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.
git 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/save)<a href="https://agentmods.dev/commands/sofumel/claude-handoff-revive/save"><img src="https://agentmods.dev/badge/commands/sofumel/claude-handoff-revive/save/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/save"><img src="https://agentmods.dev/badge/commands/sofumel/claude-handoff-revive/save.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.00019 | $0.00191 |
| Opus 5.5 | $0.00008 | $0.00076 |
| Sonnet 5.5 | $0.00004 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
save 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
Invoke the handoff-revive skill in SAVE mode.
Follow the skill's SAVE flow exactly:
- Detect language (or read
.claude/handoff/lang) - Carry forward still-relevant
goal/decisions/lessons_learnedfrom any existing handoff, then fill the schema at.claude/handoff/current.md next_actionMUST includefile:line+ exact command/edit- Run
finalize-handoff, then do the content-quality pass (step 6 of the skill's SAVE flow) — rewrite any vaguegoal/decisions/blockers/wip - Confirm in the user's language and remind: do NOT use
claude --resumeto resume
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 · 13 lines · 19 tokens per session scan A da29b6d3625b
save is a command published in the GitHub repository sofumel/claude-handoff-revive (8 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 191 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
remember
Save the current session to persistent context memory.
recall
Search past sessions stored in context memory.
audit
Audit .flow/memory/ entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry.
memory-migrate
Migrate legacy .flow/memory/{pitfalls,conventions,decisions}.md flat files into the categorized YAML schema — host agent classifies each entry directly.
memory
USE WHEN recalling past decisions, storing new insights, forgetting stale memories, linking memories, or reviewing pending memory proposals. Groups recall | learn (with optional --save-context) | forget | relate | propose.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.