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 YoungjaeDev/my-claude-plugins --skill session-handoffgit clone --depth 1 https://github.com/YoungjaeDev/my-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/youngjaedev/my-claude-plugins/session-handoff)<a href="https://agentmods.dev/skills/youngjaedev/my-claude-plugins/session-handoff"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/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/youngjaedev/my-claude-plugins/session-handoff"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/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.00095 | $0.01247 |
| Opus 5.5 | $0.00038 | $0.00499 |
| Sonnet 5.5 | $0.00019 | $0.00249 |
| Haiku 4.5 | $0.00010 | $0.00125 |
Grade B, and why
session-handoff scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Files created or modified this session — you know what you touched; do not grep to re-discover. Include `.claude/state/*.json` records a skill wrote on your behalf. How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff
Produce a repeatable end-of-session summary so the user can clear the context and start a fresh agent without losing continuity. The next agent should be able to pick up by reading this summary alone. Invoke it as /dev:session-handoff.
This is a context-handoff artifact, not a status report. The audience is a future instance of you, not a stakeholder.
When to invoke
User says: "session handoff", "wrap up session", "hand off", "handoff summary", "let's wrap up", "summarize before I clear", "세션 정리해줘", "인수인계", or any near-equivalent. Also invoke proactively when the user says they are about to clear the context without having run it yet.
How to produce the summary
- Review the full conversation, not just the last few turns. Handoffs miss things when they only summarize recent context.
- Pull state from these sources, in order. Each source is named by what it is; use whatever surface the current runtime exposes for it.
- Plan files referenced this session (Claude Code:
~/.claude/plans/; otherwise the plan path the session named). - The task list — any in-progress or pending items (Claude Code: TodoWrite state).
- Background work you started: background shells (their IDs are load-bearing for the next agent), subagents or teammates still running, workflows in flight.
- Files created or modified this session — you know what you touched; do not grep to re-discover. Include
.claude/state/*.jsonrecords a skill wrote on your behalf. - Remote objects created this session: branches pushed, PRs and issues opened, artifacts published (URLs).
- Memory or wiki files written or updated (
~/.claude/projects/<project>/memory/,.llmwiki/). - Unresolved questions — things you asked the user that never got a clear answer, or things the user asked that got deflected.
- Plan files referenced this session (Claude Code:
- Do NOT audit the filesystem. This is synthesis of what happened in THIS session. No
git log, no broad file sweeps. If you did not touch it this session, it does not belong here. - Produce the output in chat. Do not write a file. Do not update memory. Chat-only.
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.
- 1mo ago First seen · 83 lines · 95 tokens per session scan B 4a57b61c8119
session-handoff is a skill published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 1,247 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-12.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.