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 skills add mthines/agent-skills --skill handoffgit clone --depth 1 https://github.com/mthines/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/mthines/agent-skills/handoff)<a href="https://agentmods.dev/skills/mthines/agent-skills/handoff"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/handoff/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/skills/mthines/agent-skills/handoff"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/handoff.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.00139 | $0.01433 |
| Opus 5.5 | $0.00056 | $0.00573 |
| Sonnet 5.5 | $0.00028 | $0.00287 |
| Haiku 4.5 | $0.00014 | $0.00143 |
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 19d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Distill everything a fresh agent or LLM needs to continue this work — and
nothing it doesn't — into a single self-contained markdown document, written to
.agent/{branch}/handoff.md and copied to the clipboard.
The reader has zero conversation history. Write for that reader: an LLM picking this up cold, with no access to this chat, these tool results, or your scratch reasoning. Front-load the goal, name every file and command explicitly, and resolve every pronoun.
Workflow
- Parse the invocation. A free-text focus phrase (e.g.
/handoff the auth refactor) scopes the handoff to one thread of work — include only material on that thread.--briefproduces a condensed version: Goal + Next steps + top 3 files only. Default is the full document. State the chosen scope in one line before writing. - Gather the material from this session into the five section buckets below (Goal, Current state, Plan, Key files, Decisions & gotchas). Pull from what actually happened — files edited, commands run and their results, decisions made — not from what was merely discussed.
- Curate. Apply the Include / Exclude table. When unsure whether a detail earns its place, ask: would the next agent make a wrong move without it? If no, cut it.
- Resolve the output path. Run
git rev-parse --abbrev-ref HEADfor the branch. Write to.agent/{branch}/handoff.md(create the directory). If the cwd is not a git repo, fall back to.agent/handoff.md, and if.agent/is not writable, fall back to the scratchpad directory — report which path was used. - Write the file from
templates/handoff.template.md, filling every section. Omit a section entirely (heading and all) only if it is genuinely empty — never leave a placeholder or a "TODO" in the output. - Copy to clipboard. Pipe the file to
pbcopy(pbcopy < <path>). Ifpbcopyis absent (non-macOS or not onPATH), skip it and say so in the report — the file is the primary artifact; the clipboard is a convenience. - Report. Print the resolved path, whether the clipboard copy succeeded, and the section count. Do not dump the whole document back into the chat — a one-line pointer plus the path is enough.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 19d ago Changed 0bc021695e6a
- 27d ago First seen · 128 lines · 139 tokens per session scan A 2ee388b2578f
handoff is a skill published in the GitHub repository mthines/agent-skills (19 stars, last pushed today), licensed MIT. It adds 139 tokens to every session and 1,433 once invoked, about $0.0006 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-09-22.
Other skills, from other repositories
incident-postmortem
Escribe un postmortem de incidente estructurado o revisión post-incidente. Úsalo cuando se te pida escribir un postmortem, reporte de incidente, revisión P1/P2, reporte de apagón o RCA (análisis de causa raíz). Produce un postmortem sin culpables con cronología, causa raíz, factores contribuyentes, resumen de impacto…
meeting-notes
Estructura y formatea notas de reunión siguiendo las mejores prácticas de PM. Úsalo cuando te pidan crear notas de reunión, formatear notas de discusión, capturar elementos de acción, o documentar decisiones de cualquier tipo de reunión. Produce notas estructuradas con decisiones, elementos de acción (responsable +…
technical-debt-register
Documenta y prioriza un backlog de deuda técnica con impacto empresarial, estimaciones de esfuerzo y estrategia de resolución. Úsalo cuando se te pida auditar deuda técnica, crear un registro de deuda, priorizar deuda técnica para un trimestre, documentar atajos arquitectónicos o construir una hoja de ruta de…
cs-health-scorecard
Construir un cuadro de mando de salud del cliente para una cuenta específica. Úsalo cuando te pidan calificar la salud de la cuenta, evaluar el riesgo de renovación, construir un panel de salud o evaluar la probabilidad de que una cuenta se renueve o expanda. Produce un cuadro de mando de salud estructurado con estado…
stakeholder-update
Crear actualizaciones ejecutivas concisas para stakeholders usando el framework BLUF (Bottom Line Up Front). Usa cuando te pidan escribir una actualización de estado, reporte de progreso, comunicación de proyecto o briefing ejecutivo para liderazgo o stakeholders. Produce una actualización encabezada por BLUF con…
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…