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/resume)<a href="https://agentmods.dev/commands/sofumel/claude-handoff-revive/resume"><img src="https://agentmods.dev/badge/commands/sofumel/claude-handoff-revive/resume/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/resume"><img src="https://agentmods.dev/badge/commands/sofumel/claude-handoff-revive/resume.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.00021 | $0.00213 |
| Opus 5.5 | $0.00008 | $0.00085 |
| Sonnet 5.5 | $0.00004 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
resume 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 RESUME mode.
- Read
.claude/handoff/current.md(and.claude/handoff/langfor output language). - Do NOT read prior session transcripts.
- Run the
resume-receiptscript first (see SKILL.md RESUME step 3) and show the tiny load-boundary receipt before any edits. - Run the
check-freshnessscript; if it prints warnings, surface them to the user in their language. Warnings inform — they never block the resume. In the same step runstats-handoff record resume(zero-token counter for/handoff-revive:stats). - State the goal and
next_actionback to the user in 1–2 sentences. - Ask "Proceed?" before editing anything.
- After confirmation, execute
next_action.
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 · 14 lines · 21 tokens per session scan A b706ff7db627
resume is a command published in the GitHub repository sofumel/claude-handoff-revive (8 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 213 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.