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/jeffh/claude-plugins/resume_handoffgit clone --depth 1 https://github.com/jeffh/claude-pluginsWrote 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/jeffh/claude-plugins/resume_handoff)<a href="https://agentmods.dev/commands/jeffh/claude-plugins/resume_handoff"><img src="https://agentmods.dev/badge/commands/jeffh/claude-plugins/resume_handoff.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.00011 | $0.01888 |
| Opus 5 | $0.00005 | $0.00944 |
| Sonnet 5 | $0.00002 | $0.00378 |
| Haiku 4.5 | $0.00001 | $0.00189 |
Grade A, and why
resume_handoff 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume work from a handoff document
You are tasked with resuming work from a handoff document through an interactive process. These handoffs contain critical context, learnings, and next steps from previous work sessions that need to be understood and continued.
Initial Response
When this command is invoked:
-
If the path to a handoff document was provided:
- If a handoff document path was provided as a parameter, skip the default message
- Immediately read the handoff document FULLY
- Immediately read any research or plan documents that it links to under
thoughts/shared/plansorthoughts/shared/research. do NOT use a sub-agent to read these critical files. - Begin the analysis process by ingesting relevant context from the handoff document, reading additional files it mentions
- Then propose a course of action to the user and confirm, or ask for clarification on direction.
-
If a ticket number (like ENG-XXXX) was provided:
- locate the most recent handoff document for the ticket. Tickets will be located in
thoughts/shared/handoffs/ENG-XXXXwhereENG-XXXXis the ticket number. e.g. forENG-2124the handoffs would be inthoughts/shared/handoffs/ENG-2124/. List this directory's contents. - There may be zero, one or multiple files in the directory.
- If there are zero files in the directory, or the directory does not exist: tell the user: "I'm sorry, I can't seem to find that handoff document. Can you please provide me with a path to it?"
- If there is only one file in the directory: proceed with that handoff
- If there are multiple files in the directory: using the date and time specified in the file name (it will be in the format
YYYY-MM-DD_HH-MM-SSin 24-hour time format), proceed with the most recent handoff document. - Immediately read the handoff document FULLY
- Immediately read any research or plan documents that it links to under
thoughts/shared/plansorthoughts/shared/research; do NOT use a sub-agent to read these critical files. - Begin the analysis process by ingesting relevant context from the handoff document, reading additional files it mentions
- Then propose a course of action to the user and confirm, or ask for clarification on direction.
- locate the most recent handoff document for the ticket. Tickets will be located in
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 · 217 lines · 11 tokens per session scan A 9d4b2663585a
resume_handoff is a command published in the GitHub repository jeffh/claude-plugins (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 1,888 once invoked, about $0.0001 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.