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 REMvisual/claude-handoff --skill handoffgit clone --depth 1 https://github.com/REMvisual/claude-handoffWrote 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/remvisual/claude-handoff/handoff)<a href="https://agentmods.dev/skills/remvisual/claude-handoff/handoff"><img src="https://agentmods.dev/badge/skills/remvisual/claude-handoff/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/remvisual/claude-handoff/handoff"><img src="https://agentmods.dev/badge/skills/remvisual/claude-handoff/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.00039 | $0.03016 |
| Opus 5.5 | $0.00016 | $0.01206 |
| Sonnet 5.5 | $0.00008 | $0.00603 |
| Haiku 4.5 | $0.00004 | $0.00302 |
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 today.
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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff
Guards:
- Not plan mode. This skill writes files. If in Claude Code plan mode, exit first.
- Not shadowing. NEVER generate handoff-like documents freeform. Freeform summaries look right but lack chain tracking, self-validation, and evidence mining. Only this skill produces handoffs.
- Not when discussing. Only run when the user explicitly asks to CREATE a handoff right now. If ambiguous ("what does handoff do", "edit the handoff file"), ask first.
Typical use: ~75% context. You have a lot of conversation to mine — extract maximum value before closing. On 1M context that's ~750K tokens of history.
The user should not need to provide anything — /handoff alone is sufficient.
Arguments: $ARGUMENTS
Compact mode
If $ARGUMENTS contains the word compact-mode, the compact-handoff mod started this run. It replaces the conversation with this handoff when your turn ends, so the turn must finish with nothing pending:
- Run Steps 1-6 exactly as normal. Anything else in
$ARGUMENTSis the framing hint. - Step 7: one line only (file path, line count, chain seq). The compaction replaces this turn seconds later, so a full report is wasted output.
- Ask nothing in this turn. Where a step says to ask (e.g. Tier B "Any doubt"), take its stated default and note the choice in the handoff.
- Step 8: don't ask. Follow the Yes flow in
references/close-session.md(append## Session Closed, commit, print the paste prompt), skipping its step 4. - Print the paste prompt block exactly as the template has it: the
PASTE THIS INTO YOUR NEXT SESSION:header, the dashed rules, the(seq {N}, {chain_tag})line and the onboarding steps. The mod sends that block as the next prompt word for word. Never shorten it to one line, even when you reused or restored an existing handoff instead of writing a new one. - End your turn with this exact last line, path relative to the repo root:
COMPACT-HANDOFF-READY: {handoff path} - If no handoff file could be written, end with
COMPACT-HANDOFF-FAILED: {reason}instead. The mod then leaves the context untouched.
What ships with it
4 files 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.
- today Changed · +1 lines 1f019f0df7a4
- 4d ago Changed · +12 lines 5ab38c55d547
- 1mo ago First seen · 225 lines · 39 tokens per session scan A 21945d447752
handoff is a skill published in the GitHub repository REMvisual/claude-handoff (65 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 3,016 once invoked, about $0.0002 per session on Opus 5.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
sfl
Save For Later: checkpoint this window so a fresh session (or /nil) can resume it later. Use when the user types /sfl, "save for later", or "checkpoint this window". Writes a live per-window entry under /.claude/sfl/ (plus an optional durable note in the user's own memory system), then shows the green Saved-for-Later…
computer-history
Answer questions about what the user recently did on their computer — who contacted them, what they were working on, where they left off — by reading the local Computer History summaries and raw event streams.
claude-reflect
Self-learning system that captures corrections during sessions and reminds users to run /reflect to update CLAUDE.md. Use when discussing learnings, corrections, or when the user mentions remembering something for future sessions.
user-profile-keeper
Local user-profile maintenance skill for Codex, Claude Code, OpenClaw, OpenCode, and other agent harnesses. Use only when the user explicitly invokes $user-profile-keeper to create, initialize, update, query, correct, delete, export, or audit a local persistent user profile. It can extract durable collaboration…
session-handoff-prompt
Create a concise continuation prompt that a fresh agent session can paste in to resume a long or degraded session. Use when the user asks for a handoff prompt, restart prompt, continuation prompt, context transfer, fresh-session resume, or a compact summary for opening a new session. Do not use for ordinary summaries…
principle-guard-the-context-window
Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.