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 OneWave-AI/claude-skills --skill session-handoffgit clone --depth 1 https://github.com/OneWave-AI/claude-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/onewave-ai/claude-skills/session-handoff)<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/session-handoff"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-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/onewave-ai/claude-skills/session-handoff"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-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.00083 | $0.00962 |
| Opus 5 | $0.00042 | $0.00481 |
| Sonnet 5 | $0.00017 | $0.00192 |
| Haiku 4.5 | $0.00008 | $0.00096 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff
A session ends three ways: the context fills up, the person leaves, or the work moves to someone else. All three lose the same thing — the reasoning that never made it into a file. This skill writes that reasoning down before it evaporates.
Core Behavior
Write a handoff file, do not summarize in chat. Chat scrolls away; a file survives a /clear, a crash, and a different person opening the repo tomorrow.
Default path: HANDOFF.md at the repo root, or docs/handoff/<yyyy-mm-dd>-<topic>.md if the repo already has a docs convention. If a handoff file exists, append a new dated section rather than overwriting — the history of what was tried is half the value.
What Goes In It
Write these sections in this order. Skip a section only when it is genuinely empty.
Goal. One sentence: what this work is supposed to achieve, in the user's terms, not the ticket's.
State. What is done, what is half-done, what has not been started. Be specific about half-done — "auth works, but the refresh-token path is stubbed and returns a fixed string" beats "auth in progress".
Files touched. Path plus one line on what changed and why. Include files you read and decided not to change when the decision was non-obvious.
Decisions and why. The choices a reasonable person would question. Each one: what was chosen, what was rejected, and the reason. This is the section that saves the next session an hour.
Dead ends. What was tried and did not work. Name the failure mode. Without this, the next session repeats it.
Next step. The single next action, concrete enough to start on immediately. Not "continue the refactor" — "extract parseInvoice from billing.ts:210 into its own module, then point the three callers at it".
Open questions. Anything waiting on a human. Name who, and what the question is.
How to Gather It
Prefer evidence over memory:
git statusandgit diff --statfor what actually changed on disk.git log --oneline -15for what landed.- Test/build output from the last run, if there was one.
- The user's own words for the goal — quote them rather than paraphrasing into corporate language.
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 · 91 lines · 83 tokens per session scan A 4a456f51ae24
session-handoff is a skill published in the GitHub repository OneWave-AI/claude-skills (301 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 962 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-09-20.
Other skills, from other repositories
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
after-action-report
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event.…
mass-ulw
Drives dependency-ordered child work through the native workflow tool, one run per phase with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
beta-program-management
Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional…
okr-design
OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the difference between sandbagged OKRs (always 100%) and aspirational OKRs (always 30%) and stretch OKRs (genuine ambition…