successor-handoff

successor-handoff is a skill for Claude Code from wan-huiyan/context-baton. It costs 163 tokens per session (4,170 once invoked), scanned A, original, MIT.

A workflow pattern for running autonomous coding or research work for many hours using several agents and files as shared memory. A successor is a fresh agent that continues a task when the current agent's context becomes too large.

In plain words
What is it for?
Use it for overnight research, multi-track experiments, long database investigations, and other extended autonomous workflows.
Why use it?
It avoids filling one conversation with every tool result and reduces the need for a person to pause and restart long jobs.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the successor-handoff plugin — 1 skill shipped together

Good fit Use it for overnight research, multi-track experiments, long database investigations, and other extended autonomous workflows.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wan-huiyan/context-baton/successor-handoff
Install

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.

Any agent
npx skills add wan-huiyan/context-baton --skill successor-handoff
Clone the repo
git clone --depth 1 https://github.com/wan-huiyan/context-baton

Made for: Claude Code.

Or install successor-handoff, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for successor-handoff

README.md
[![agentmods](https://agentmods.dev/badge/skills/wan-huiyan/context-baton/successor-handoff/github.svg)](https://agentmods.dev/skills/wan-huiyan/context-baton/successor-handoff)
Your own site
<a href="https://agentmods.dev/skills/wan-huiyan/context-baton/successor-handoff"><img src="https://agentmods.dev/badge/skills/wan-huiyan/context-baton/successor-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.

agentmods 80×15 button for successor-handoff

Your own site · 80×15
<a href="https://agentmods.dev/skills/wan-huiyan/context-baton/successor-handoff"><img src="https://agentmods.dev/badge/skills/wan-huiyan/context-baton/successor-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 163 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,170 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00163 $0.04170
Opus 5 $0.00081 $0.02085
Sonnet 5 $0.00033 $0.00834
Haiku 4.5 $0.00016 $0.00417

Measured 10d ago against content hash 4626a468f139, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

successor-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 10d 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.

plugins/successor-handoff/SKILL.md · 265 lines

How it starts

The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Successor Handoff

A pattern for running many-hour autonomous workflows without hitting a single context window.

Three rules, one parent, many successor hops. The parent never fills up because it reads only status files. Each track's subagent stays lean via file-first discipline. When a subagent's context does start to swell, a fresh successor spawns in seconds with the filesystem as its memory — no human in the loop, no narrative compression.

The Problem

Autonomous workflows that need many hours of wall-clock time — overnight research, multi-track experiments, 10-hour BigQuery exploration — cannot fit in a single Claude context window. Two naive patterns exist, and both fail:

  1. Work until context fills, then session-handoff to a human, then resume. Costs minutes-to-hours per round-trip. Requires a human at an unpredictable time. Each handoff is a lossy narrative compression.
  2. Keep one giant context alive. Claude degrades before it errors. Tool outputs that never get pruned clog the prompt. Quality drops quietly.

The pattern in this skill replaces both. The parent orchestrator is permanently lean (reads only status files, never query outputs), so it isn't the thing filling up. Each track is a subagent using disk as memory (per planning-with-files). When a subagent does get stretched, a fresh successor is dispatched in seconds with a resume prompt pointing at the state directory. No human needed. No narrative summary needed. The file system is the knowledge.

When to Use

digraph when {
  "Autonomous work that may exceed one context window?" [shape=diamond];
  "Agent-to-agent handoff mid-run?" [shape=diamond];
  "End-of-run delivery to a human?" [shape=diamond];
  "successor-handoff (this skill)" [shape=box, style=filled, fillcolor=lightyellow];
  "session-handoff" [shape=box];
  "Normal conversation — no handoff pattern" [shape=box];

  "Autonomous work that may exceed one context window?" -> "Agent-to-agent handoff mid-run?" [label="yes"];
  "Autonomous work that may exceed one context window?" -> "Normal conversation — no handoff pattern" [label="no"];
  "Agent-to-agent handoff mid-run?" -> "successor-handoff (this skill)" [label="yes"];
  "Agent-to-agent handoff mid-run?" -> "End-of-run delivery to a human?" [label="no"];
  "End-of-run delivery to a human?" -> "session-handoff" [label="yes"];
  "End-of-run delivery to a human?" -> "Normal conversation — no handoff pattern" [label="no"];
}

Read the full file on GitHub · 265 lines

Files

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.

Changes

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.

  1. 10d ago First seen · 265 lines · 163 tokens per session scan A 4626a468f139

Subscribe to this mod's changes

successor-handoff is a skill published in the GitHub repository wan-huiyan/context-baton (1 stars, last pushed 1mo ago), licensed MIT. It adds 163 tokens to every session and 4,170 once invoked, about $0.0008 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.

Related

Other skills, from other repositories

high-output-management

Manage for output using Grove's "High Output Management": a manager's output is their organization's output, raised by high-leverage activities. Use when the user mentions "high output management", "managerial leverage", "one-on-ones", "1:1 agenda", "OKRs", "performance review", "task-relevant maturity", "delegation"…

wondelai/skills · 176 tokens

37signals-way

Build lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat…

wondelai/skills · 177 tokens

drive-motivation

Design motivation systems using Autonomy, Mastery, and Purpose (AMP) for products and teams. Use when the user mentions "intrinsic motivation", "gamification isnt working", "rewards arent working", "autonomy", "mastery", "purpose-driven", "my team is disengaged", or "how do I motivate people". Also trigger when…

wondelai/skills · 130 tokens

claude-code-bash-patterns

Claude Code Bash tool patterns with hooks, automation, git workflows. Use for PreToolUse hooks, command chaining, CLI orchestration, custom commands, or encountering bash permissions, command failures, security guards, hook configurations.

secondsky/claude-skills · 52 tokens

sitrep-panel

Keep a live local HTML report updated as you work on a task — a status board, a running "what's happening now" narrative, screenshots, and a newest-first log — served on localhost so the user can watch progress in a browser tab instead of reading the transcript. Use when the user invokes /sitrep-panel, asks for a…

dbl8005/sitrep-panel · 101 tokens

promote

Turn a scratch script into a permanent tool this repo keeps. Use when a check, report, or analysis has proved worth running more than once.

ArcticFox2029/chamnan · 29 tokens