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/thepushkarp/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/thepushkarp/handoff/resume)<a href="https://agentmods.dev/commands/thepushkarp/handoff/resume"><img src="https://agentmods.dev/badge/commands/thepushkarp/handoff/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/thepushkarp/handoff/resume"><img src="https://agentmods.dev/badge/commands/thepushkarp/handoff/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.00008 | $0.00480 |
| Opus 5.5 | $0.00003 | $0.00192 |
| Sonnet 5.5 | $0.00002 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
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
Resume work from an existing handoff document at docs/handoff/HANDOFF.md.
Behavior
Default mode (no arguments): Display the handoff content and ask the user how they want to proceed.
Auto mode (--auto flag): Automatically inject the context and begin working on the next steps.
Steps
-
Check for Handoff File Read docs/handoff/HANDOFF.md if it exists.
-
Parse Most Recent Handoff The file may contain multiple handoff entries (appended with timestamps). Focus on the most recent handoff entry (the last
## Handoff: [TIMESTAMP]section in the file). -
Based on Mode:
If no arguments (default mode):
- Display a summary of the most recent handoff:
- When it was created
- Current task state
- Key decisions made
- Any blockers
- Next steps listed
- Ask the user: "How would you like to proceed? I can:
- Start working on the next steps
- Review the full handoff details first
- Do something else - please specify"
If
--autoflag provided:- Silently load the context
- Set up todos from the "Next Steps" section using TodoWrite
- Begin working on the first next step immediately
- Inform the user: "Resuming from handoff created at [TIMESTAMP]. Starting work on: [first next step]"
- Display a summary of the most recent handoff:
-
Handle Missing Handoff If docs/handoff/HANDOFF.md doesn't exist:
- Inform the user: "No handoff file found at docs/handoff/HANDOFF.md. Would you like to describe your current task so I can help you continue?"
Important Notes
- Pay attention to the "Critical Context" section - it contains gotchas and important info
- Respect any blockers mentioned - ask about their status before proceeding
- The "Key Decisions" section contains rationale that should guide continued work
- If multiple handoffs exist, you can offer to show history if user asks
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 · 53 lines · 8 tokens per session scan A 42f5946bd146
resume is a command published in the GitHub repository thepushkarp/handoff (12 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 480 once invoked, about $0.0000 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
refresh
Auto-enumerate the agent-runnable To-Do set and write it to state/todo-ids.json. No arguments. The operator's only job upstream is to mark rows in Notion with Exec=Agent; refresh then fetches them via the Notion REST API and the sidecar is the enumeration substrate for run.
start
Move To-Do -> In Progress and emit the kickoff brief.
tree
Emit a compact indented view of the active task hierarchy and refresh state/task-tree.json. This is the primary tool for understanding the board's shape before adding new work.
scaffold
The single-shot setup command. Builds the entire Notion workspace from scratch — Hub page, Tasks database with the full schema below, General Guidance page, Resources page, default corpus pages (General, Recurring), and every linked DB view. There is no public Notion template to duplicate; this command IS the setup.…
suggest
Add a row in Suggestion status. Structure check runs inside suggest — the subagent enforces it, not just the orchestrator. The orchestrator decides the shape (which parent, whether a container is needed); suggest verifies that decision was made rather than silently creating a root-level row.
discuss
Begin clarification on a Suggestion. Flips status to Discussion and prepares the agent to ask clarifying questions.