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/vaayne/agent-kit/handoffnpx skills add vaayne/agent-kit --skill handoffgit clone --depth 1 https://github.com/vaayne/agent-kitWhat 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.00068 | $0.00486 |
| Opus 5 | $0.00034 | $0.00243 |
| Sonnet 5 | $0.00014 | $0.00097 |
| Haiku 4.5 | $0.00007 | $0.00049 |
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 2d 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
Handoff
Generate a session summary and write it to handoff.md so a new session can pick up where this one left off.
Workflow
- Analyze the current session — gather goals, progress, decisions, file changes, blockers, and next steps.
- Write
handoff.md— save the summary tohandoff.mdin the project root (overwrite if exists). - Guide the user — tell the user to start a new session with:
read handoff.md and continue the work.
Handoff File Template
Write handoff.md using this structure:
# Handoff
## Goal
[Original objective of this session]
## Progress
- [What was completed]
- [What was partially done]
## Key Decisions
- [Decision 1 and why]
- [Decision 2 and why]
## Files Changed
- `path/to/file1` — [what changed]
- `path/to/file2` — [what changed]
## Current State
[Where things stand right now — what works, what doesn't]
## Blockers / Gotchas
- [Any issues, edge cases, or warnings for the next session]
## Next Steps
1. [Concrete next action]
2. [Follow-up action]
Guidelines
- Be self-contained — the new session must understand the full picture without the old conversation.
- Be concise — include only what's relevant; skip empty sections.
- Focus on decisions and rationale — what was decided and why, not the full discussion.
- List concrete files with context — path + what changed, not just paths.
- State next steps as actionable tasks — clear enough to execute immediately.
After Writing
Confirm the file was written and instruct the user:
handoff.mdhas been saved. To continue in a new session, start with:read handoff.md and continue the work
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.
- 2d ago First seen · 73 lines · 68 tokens per session scan A 45641129e3e2
handoff is a skill published in the GitHub repository vaayne/agent-kit (53 stars, last pushed 5d ago), licensed MIT. It adds 68 tokens to every session and 486 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…