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/willseltzer/claude-handoff/resumegit clone --depth 1 https://github.com/willseltzer/claude-handoffWrote 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/willseltzer/claude-handoff/resume)<a href="https://agentmods.dev/commands/willseltzer/claude-handoff/resume"><img src="https://agentmods.dev/badge/commands/willseltzer/claude-handoff/resume.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.1 | $0.00007 | $0.00359 |
| Opus 5 | $0.00003 | $0.00179 |
| Sonnet 5 | $0.00001 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
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 6d 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
Resume work from a handoff created by another AI agent.
1. Find and Read the Handoff
Look for the handoff document:
- If
$ARGUMENTSis provided, read that path - Otherwise, check for
HANDOFF.mdin the current directory - If not found, ask the user for the path
Read the entire handoff document carefully.
2. Verify State Hasn't Drifted
Run git status and git log --oneline -3 to check:
- Is the branch the same as documented?
- Have there been commits since the handoff was created?
- Are there uncommitted changes not mentioned in the handoff?
If state has drifted significantly, warn the user:
"The repo has changed since this handoff was created. [describe changes]. Should I proceed with the handoff context anyway, or would you like to describe what changed?"
3. Summarize to the User
Give a brief summary (not the whole document):
Resuming from handoff: [title]
Goal: [1 sentence]
Status: [X of Y tasks complete]
Next: [First item from Resume Instructions]
Ready to continue?
4. Heed the Warnings
Pay special attention to:
- Failed Approaches - Don't repeat these mistakes
- Warnings - Respect gotchas from the previous agent
- Key Decisions - Follow established patterns unless user asks to change
5. Continue the Work
Start with the first item in "Resume Instructions" unless the user redirects.
If the handoff is unclear on something critical, ask the user rather than guessing.
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.
- 6d ago First seen · 52 lines · 7 tokens per session scan A c6760b806f74
resume is a command published in the GitHub repository willseltzer/claude-handoff (143 stars, last pushed 8mo ago), licensed MIT. It adds 7 tokens to every session and 359 once invoked, about $0.0000 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.