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 bhaumikmaan/claude-code-master-skills --skill session-handoffgit clone --depth 1 https://github.com/bhaumikmaan/claude-code-master-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/bhaumikmaan/claude-code-master-skills/session-handoff)<a href="https://agentmods.dev/skills/bhaumikmaan/claude-code-master-skills/session-handoff"><img src="https://agentmods.dev/badge/skills/bhaumikmaan/claude-code-master-skills/session-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/bhaumikmaan/claude-code-master-skills/session-handoff"><img src="https://agentmods.dev/badge/skills/bhaumikmaan/claude-code-master-skills/session-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.00058 | $0.01040 |
| Opus 5 | $0.00029 | $0.00520 |
| Sonnet 5 | $0.00012 | $0.00208 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
session-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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff
CRITICAL: Preserve the template structure exactly. Never modify, delete, or add section headers. Never modify the italic section descriptions. Only update the content below each section's description line.
Session Title Rules
Generate a concise, sentence-case title (3-7 words) that captures the main topic or goal.
Good titles:
- "Fix login button on mobile"
- "Add OAuth authentication"
- "Debug failing CI tests"
- "Refactor API client error handling"
Bad titles:
- "Code changes" — too vague, doesn't identify the session
- "Investigate and fix the issue where the login button does not respond on mobile devices" — too long
- "Fix Login Button On Mobile" — wrong case (use sentence case, not Title Case)
Session Notes Template
The notes file uses a fixed template. Each section has two parts that must be preserved exactly:
- The section header (line starting with
#) - The italic description line (the
_italicized text_immediately after the header)
You ONLY update the content that comes AFTER these two preserved lines.
Required Sections
| Section | What to Write |
|---|---|
| Session Title | 5-10 word descriptive title, info-dense, no filler |
| Current State | What's being worked on RIGHT NOW. Pending tasks. Immediate next steps. This is the most critical section for continuity. |
| Task specification | What the user asked to build. Design decisions and explanatory context. |
| Files and Functions | Important files, what they contain, why they're relevant. |
| Workflow | Bash commands usually run and in what order. How to interpret output if not obvious. |
| Errors & Corrections | Errors encountered, how fixed. What the user corrected. What approaches failed. |
| Codebase and System Documentation | Important system components. How they work/fit together. |
| Learnings | What worked, what didn't, what to avoid. Don't duplicate items from other sections. |
| Key results | If the user asked for specific output (answer, table, document), repeat the exact result. |
| Worklog | Step-by-step, what was attempted and done. Very terse summary per step. |
What ships with it
1 file 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.
- 9d ago First seen · 89 lines · 58 tokens per session scan A 217f52b956d3
session-handoff is a skill published in the GitHub repository bhaumikmaan/claude-code-master-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 58 tokens to every session and 1,040 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-31.
Other skills, from other repositories
distill-feedback
A process for turning corrections you give an agent into lasting working rules. It reviews saved conversations and asks for approval before changing those rules.
contextpilot
Optimize document ordering in LLM context for better retrieval performance.
knowledge-base
Retrieves and updates project-specific prompt knowledge from comparison evidence and user feedback. Use only for prompt analysis or post-comparison learning within a Rashomon evaluation.
obsidian-vault
Create, edit, and audit notes in an Obsidian vault. Handles frontmatter properties, wikilinks, embeds, callouts, tasks, block references, tags, and Mermaid diagrams. Plugin-aware: Dataview queries and inline fields, Tasks emoji syntax, Kanban boards, Meta Bind fields, Templater templates, Bases schemas, and Canvas…
compress
Prompt-Studio memory compressor. Shrinks CLAUDE.md, todo lists, and preference files into Prompt-Studio's lean format to cut input tokens on every load. Preserves all technical substance, code, URLs, and structure. Compressed output overwrites the original; human-readable backup stored out-of-tree as FILE.original.md…
context-economy
Automatically prepare fidelity-first, bounded context when users paste text, attach files or folders, provide webpages or PDFs for Markdown conversion, continue long conversations, or supply documents containing images and complex tables. Route each input through Text, Hybrid, or Source; reduce exact or…