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 skills/marchatton/agent-skills/handoffnpx skills add marchatton/agent-skills --skill handoffgit clone --depth 1 https://github.com/marchatton/agent-skillsWrote 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/skills/marchatton/agent-skills/handoff)<a href="https://agentmods.dev/skills/marchatton/agent-skills/handoff"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/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.1 | $0.00035 | $0.00577 |
| Opus 5 | $0.00017 | $0.00289 |
| Sonnet 5 | $0.00007 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/handoff
Purpose: package the current state so the next agent (or future you) can resume quickly.
Persist the handoff note (always)
- Determine repo root.
- Prefer:
git rev-parse --show-toplevel - Fallback: current working directory
- Prefer:
- Use a git-tracked handoff area so it can be reused later (including via automations):
- If the work is tied to a dossier under
docs/04-projects/.../<dossier>/: write to<dossier>/tmp-handoffs/. - Otherwise (non-dossier or cross-dossier): write to
docs/98-tmp/handoffs/.
- If the work is tied to a dossier under
- Create the folder if missing.
- Generate filename using the handoff time:
handoff_YYYY-MM-DD_HH-MM-SS_<3-5 words>.md- Choose 3–5 words that describe the work or topic.
- Prefer lowercase kebab-case for the words (avoid spaces and special characters).
- Write the handoff checklist content into that markdown file.
- Echo the saved file path at the top of the handoff output.
Handoff checklist content (write in this order)
- Scope/status: what you were doing, what’s done, what’s pending, and any blockers.
- Working tree:
git status -sbsummary and whether there are local commits not pushed. - Branch/PR: current branch, relevant PR number/URL, CI status if known.
- Running processes: list tmux sessions/panes and how to attach:
- Example:
tmux attach -t codex-shellortmux capture-pane -p -J -t codex-shell:0.0 -S -200 - Note dev servers, tests, debuggers, background scripts.
- Example:
- Tests/checks: which commands were run, results, and what still needs to run.
- Next steps: ordered bullets the next agent should do first.
- Risks/gotchas: any flaky tests, credentials, feature flags, or brittle areas.
Output format
- Start with: “Saved handoff: ”
- Then a concise bullet list (copy/paste friendly).
- Include copy/paste tmux commands for any live sessions.
Notes
- Prefer writing the note even if the session continues. A fresh thread can be started at any time without losing state.
- If file write is not possible, print the handoff checklist in chat and ask the user to save it into the git-tracked handoff area.
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 · 48 lines · 35 tokens per session scan A b48b9f8e1ada
handoff is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 577 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…