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 agentmods add skills/remvisual/claude-handoff/handoffnpx 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.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 | $0.00039 | $0.02672 |
| Opus 5 | $0.00019 | $0.01336 |
| Sonnet 5 | $0.00008 | $0.00534 |
| Haiku 4.5 | $0.00004 | $0.00267 |
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 5d 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 — 225 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
Agent Strategy
Parallelize independent research. Launch in one message.
| What | Mode | Why |
|---|---|---|
| Step 1A (git/beads/ls) | Parallel Bash, never agents | Cheap commands; agent bootup wastes 15K+ each |
| Step 1B context agents (OV, stale-refs, bible) | Parallel Bash inline; agents only if parent handoff >500 lines | Independent research |
| Step 1C (conversation mining) | Main agent only | Only you have the history |
| Steps 5+6 (beads/memory writes) | Parallel Bash | Independent writes |
Step 1: Deep Context Gathering
1A: External State (parallel Bash — never agents)
Run in one message as inline Bash calls:
| Commands | Returns |
|---|---|
git log --oneline -20, git diff --stat, git status -s | head -30, git branch --show-current |
Branch, recent commits, uncommitted changes |
bd list --status=in_progress, bd list --status=open --priority=0,1, bd stats (skip if bd unavailable) |
Active/open beads |
ls plans/handoffs/, ls .claude/handoffs/, ls plans/*.md |
Existing handoff files |
1B: Chain Detection
Resolve the chain tag (use first that applies):
- Epic exists → use epic name/ID
- 1-4 beads → use all bead IDs (e.g.,
myproject-xxxx, myproject-yyyy) - 5+ beads → pick 2-3 most relevant to the primary work stream
- No beads/epic → generate fallback:
python -c "import secrets; print(secrets.token_hex(4))"→standalone-{hex}
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.
- 5d ago First seen · 225 lines · 39 tokens per session scan A 21945d447752
handoff is a skill published in the GitHub repository REMvisual/claude-handoff (48 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 2,672 once invoked, about $0.0002 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-30.
Other skills, from other repositories
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
client-context-system
Sets up a complete per-client workspace in Cowork with isolated context, preferences, deliverable templates, running notes, decision log, and automatic status reporting. For consultants, agencies, and professional services. Useful when onboarding a new client, during engagement kickoffs, for organizing existing client…
context-manager
Teaches you how to break large tasks into stages, save your place between sessions, and recover smoothly when a task gets interrupted. Use when planning a multi-day project, for breaking down large work into manageable stages, during recovery from an interrupted session, when managing complex ongoing work, or when the…
memory-system
Sets up a file-based memory system so Cowork always knows who you are, how you work, and where your projects stand. For eliminating repetitive re-introductions at session start, when building persistent context across multiple projects, or during initial Cowork onboarding. Use when the user says "claude doesn't…
context-engine
../../../c-level-advisor/skills/context-engine/SKILL.md.
agent-memory-mcp
A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).