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 ao92265/claude-code-playbook --skill handoffgit clone --depth 1 https://github.com/ao92265/claude-code-playbookWrote 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/ao92265/claude-code-playbook/handoff)<a href="https://agentmods.dev/skills/ao92265/claude-code-playbook/handoff"><img src="https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/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.00083 | $0.00652 |
| Opus 5 | $0.00042 | $0.00326 |
| Sonnet 5 | $0.00017 | $0.00130 |
| Haiku 4.5 | $0.00008 | $0.00065 |
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 7d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff
Create a structured handoff document so the next Claude Code session (or another developer) can pick up exactly where you left off.
Steps
-
Summarize what was accomplished:
- List files created, modified, or deleted
- Describe each change in one sentence
- Note any tests added or modified
-
Document what's left to do:
- Remaining tasks from the original request
- Known issues discovered during implementation
- Tests that still need to be written
- Edge cases identified but not yet handled
-
Record decisions made:
- Architecture or design choices and why they were made
- Alternatives that were considered and rejected (with reasons)
- Trade-offs accepted (e.g., "chose simplicity over performance because...")
-
Flag gotchas and warnings:
- Anything that's fragile or could break easily
- Dependencies on external systems or specific configurations
- Environment-specific requirements (env vars, services, ports)
- Known limitations of the current implementation
-
Capture the current state:
- Branch name and last commit hash
- Test results (passing/failing counts)
- Build status (clean or known errors)
- Any running processes or servers that need to be stopped/started
-
Write to SESSION_NOTES.md:
- Save in the project root as
SESSION_NOTES.md - Replace contents if file already exists (don't append)
- Keep under 50 lines — concise is better than comprehensive
- Include date and time at the top
- Save in the project root as
Output Format
# Session Handoff — [DATE]
## Completed
- [file]: [what changed]
## Remaining
- [ ] [task]
## Decisions
- [decision]: [rationale]
## Gotchas
- [warning]
## State
- Branch: [name] @ [hash]
- Tests: [X passing, Y failing]
- Build: [clean/errors]
Important
- Replace, don't append. SESSION_NOTES.md should reflect the latest session only.
- Be specific. "Fixed the auth bug" is useless. "Changed token expiry from 1h to 24h in src/auth/config.ts" is useful.
- Include the why. Future sessions need context, not just facts.
- Keep it short. If the summary exceeds 50 lines, you're including too much detail.
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.
- 7d ago First seen · 86 lines · 83 tokens per session scan A 213411f657fc
handoff is a skill published in the GitHub repository ao92265/claude-code-playbook (10 stars, last pushed 20d ago), licensed MIT. It adds 83 tokens to every session and 652 once invoked, about $0.0004 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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…
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…