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/pandysp/claude-plugins/handoffnpx skills add pandysp/claude-plugins --skill handoffgit clone --depth 1 https://github.com/pandysp/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/skills/pandysp/claude-plugins/handoff)<a href="https://agentmods.dev/skills/pandysp/claude-plugins/handoff"><img src="https://agentmods.dev/badge/skills/pandysp/claude-plugins/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.00124 | $0.00903 |
| Opus 5 | $0.00062 | $0.00451 |
| Sonnet 5 | $0.00025 | $0.00181 |
| Haiku 4.5 | $0.00012 | $0.00090 |
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 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff: write a durable handoff
The work is done. Now write a handoff that serves the next reader without forcing them to dig through the diff.
A good handoff answers five questions in order:
- What was built: in plain language, not commit-list paraphrase.
- Why this work exists: the motivating problem, user need, or constraint that triggered it.
- Key decisions and rationale: the choices that shaped the work, alternatives considered.
- What specifically changed and why: for code: files and their purpose. For docs/plans/memos: artifacts produced and what each is for.
- Suggested next steps: follow-ups, deferred work, known gaps, things to watch.
The reader could be a code reviewer, future-you in three months, or a teammate picking up the thread. Write so any of them gets oriented in under a minute.
Standard PR shape
What was built
[2–4 sentences. What the change does, in plain language]
Why
[the motivating problem, user need, or constraint that triggered the work]
Key decisions
- [decision]: chose X over Y because Z
Files modified
path/to/file: [purpose of this file's change]Test plan
- [how to verify. Concrete steps, not "test the feature"]
- [edge cases worth checking]
Next steps
- [follow-up]: [why it's deferred or when it matters]
For shorter handoffs (commit messages, slack updates, memory notes), compress to the parts that matter. For longer ones (design docs, ADRs), expand "Why" and "Key decisions" with rationale.
For non-code handoffs (memos, design docs, memory notes), keep questions 1–3 and 5; replace "Files modified" with whatever artifacts were produced; drop "Test plan" unless verification is meaningful.
Adapt to the audience
- Code reviewer: technical, structured. Focus on what to look at and why each part matters.
- Future you: context-rich, with decisions and rationale. No shorthand that depends on session memory.
- Stakeholder: plain language, outcome-focused, less jargon.
- Memory note: terse; capture only what couldn't be derived from the current state of the code or notes.
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 · 63 lines · 124 tokens per session scan A 276300cb4c5a
handoff is a skill published in the GitHub repository pandysp/claude-plugins (5 stars, last pushed 13d ago), licensed MIT. It adds 124 tokens to every session and 903 once invoked, about $0.0006 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…