A handoff document is a short record of the current conversation, work status, blockers, and useful links for another coding agent.

Use it when pausing work, changing agents, or handing a task to a teammate. It saves the document with a descriptive filename and reports where it was saved.

It prevents the next agent from having to reread the entire conversation or repeat abandoned investigations. It also preserves important context when work changes hands.

handoff — Skill for Claude Code by MithunWijayasiri

Install

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.

Any agent

npx skills add MithunWijayasiri/dotclaude --skill handoff

Clone the repo

git clone --depth 1 https://github.com/MithunWijayasiri/dotclaude

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mithunwijayasiri/dotclaude/handoff/github.svg)](https://agentmods.dev/skills/mithunwijayasiri/dotclaude/handoff)

Your own site

<a href="https://agentmods.dev/skills/mithunwijayasiri/dotclaude/handoff"><img src="https://agentmods.dev/badge/skills/mithunwijayasiri/dotclaude/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mithunwijayasiri/dotclaude/handoff"><img src="https://agentmods.dev/badge/skills/mithunwijayasiri/dotclaude/handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 508 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00019	$0.00508
Opus 5	$0.00010	$0.00254
Sonnet 5	$0.00004	$0.00102
Haiku 4.5	$0.00002	$0.00051

Measured 9d ago against content hash 9cefc53dbe35, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 9d 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.

skills/handoff/SKILL.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Summarise this conversation for a fresh agent to continue. Save to ~/Downloads/ with a descriptive hyphenated filename, like handoff-TICKETID.md or handoff-topic.md. If that name already exists, append a timestamp instead of overwriting. If the folder is missing or unwritable, ask for another destination. Report the saved path.

Link to existing artifacts (PRDs, plans, ADRs, issues, commits, diffs) instead of copying their content.

Keep the doc compact by excluding:

Exploratory questions ("how does X work?", "explain this code")
Cancelled or abandoned work — branches, experiments, approaches that were started but dropped
Dead-end debugging — investigation paths that led nowhere
Failed attempts — exclude them unless they explain the current state, reveal a constraint, or prevent repeating the same path
Tool/command usage details — focus on results, not mechanics
Fully resolved issues — exclude them unless the resolution affects future work
Off-topic tangents — side discussions unrelated to the main work
Redundant iterations — multiple rounds of the same fix/tweak

Include:

Current state — what's working, what's broken, what's in progress
Blockers — anything stopping progress
Decisions made — architectural choices, trade-offs accepted
Next steps — what needs to happen next
Open questions — unresolved decisions the next agent should address
Key file paths — locations of relevant code/configs

Use this structure:

Handoff: [Topic]

Context

[1-2 sentences on what we were working on]

Current State

[What's working, what's broken, what's in progress]

Mark assumptions and unverified claims explicitly.
Record the latest validation status, including failures and checks not run.

Blockers

[Anything stopping progress]

Decisions Made

[Key choices and trade-offs]

Next Steps

[Prioritized list of concrete actions, including dependencies or conditions when a step cannot start immediately]

Open Questions

[Unresolved decisions for the next agent]

Read the full file on GitHub · 60 lines

Changes

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.

9d ago First seen · 60 lines · 19 tokens per session scan A 9cefc53dbe35

Subscribe to this mod's changes

handoff is a skill published in the GitHub repository MithunWijayasiri/dotclaude (2 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 508 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-31.

Productivity

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

handoff