continue-handoff

continue-handoff is a command for Claude Code from vanzan01/claude-code-sub-agent-collective. It costs 0 tokens per session (716 once invoked), scanned B, original, MIT.

A command that checks whether an interrupted agent handoff has pending delegation information in `.claude/handoff/NEXT_ACTION.json`.

In plain words
What is it for?
Use it to inspect pending handoffs, view the target agent and context, and resume the next workflow step.
Why use it?
It shows where a paused handoff stopped and which agent should continue it.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: mentions subagents; mentions Claude Code.

Good fit Use it to inspect pending handoffs, view the target agent and context, and resume the next workflow step.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/vanzan01/claude-code-sub-agent-collective/continue-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.

Clone the repo
git clone --depth 1 https://github.com/vanzan01/claude-code-sub-agent-collective

Made for: Claude Code.

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 continue-handoff

README.md
[![agentmods](https://agentmods.dev/badge/commands/vanzan01/claude-code-sub-agent-collective/continue-handoff/github.svg)](https://agentmods.dev/commands/vanzan01/claude-code-sub-agent-collective/continue-handoff)
Your own site
<a href="https://agentmods.dev/commands/vanzan01/claude-code-sub-agent-collective/continue-handoff"><img src="https://agentmods.dev/badge/commands/vanzan01/claude-code-sub-agent-collective/continue-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 continue-handoff

Your own site · 80×15
<a href="https://agentmods.dev/commands/vanzan01/claude-code-sub-agent-collective/continue-handoff"><img src="https://agentmods.dev/badge/commands/vanzan01/claude-code-sub-agent-collective/continue-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 716 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00000 $0.00716
Opus 5.5 $0.00000 $0.00286
Sonnet 5.5 $0.00000 $0.00143
Haiku 4.5 $0.00000 $0.00072

Measured 2mo ago against content hash 24a1aaf358ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

continue-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 2mo 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.

cat .claude/handoff/NEXT_ACTION.json | jq '.'
templates/commands/continue-handoff.md · 98 lines

How it starts

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

Continue Agent Handoff Workflow

Resume an interrupted agent handoff workflow by checking for pending delegation context.

What This Does

Checks for pending handoff context and resumes the workflow where it left off:

  • Reads .claude/handoff/NEXT_ACTION.json for pending delegations
  • Displays current handoff status and target agent
  • Provides commands to continue the workflow
  • Shows recent handoff logs for context

Usage

Simply run this command and it will check current state and provide next steps.

Check Current Status

# Check if there's a pending handoff
if [ -f .claude/handoff/NEXT_ACTION.json ]; then
  echo "📋 PENDING HANDOFF FOUND:"
  cat .claude/handoff/NEXT_ACTION.json | jq '.'
  echo ""
  echo "🎯 NEXT ACTION:"
  echo "Use the $(cat .claude/handoff/NEXT_ACTION.json | jq -r '.target_agent') subagent to continue the workflow."
else
  echo "✅ No pending handoffs - workflow is clear"
fi

Resume Workflow

# Get target agent from context file
TARGET_AGENT=$(cat .claude/handoff/NEXT_ACTION.json | jq -r '.target_agent' 2>/dev/null)
CONTEXT=$(cat .claude/handoff/NEXT_ACTION.json | jq -r '.context' 2>/dev/null)

if [ -n "$TARGET_AGENT" ] && [ "$TARGET_AGENT" != "null" ]; then
  echo "🚀 RESUMING WORKFLOW:"
  echo "Target Agent: $TARGET_AGENT"
  echo "Context: $CONTEXT"
  echo ""
  echo "📝 COMMAND TO CONTINUE:"
  echo "Use the $TARGET_AGENT subagent to continue from the previous handoff context."
else
  echo "❌ No valid handoff context found"
fi

When to Use

  • After Interruption: When workflow was stopped mid-execution
  • Session Restart: After closing and reopening Claude Code
  • Network Issues: After connection problems during handoffs
  • Manual Break: When you manually stopped to check something
  • Debugging: To see current workflow state

What You'll See

If Handoff Pending:

{
  "timestamp": "2025-08-11T14:55:18+08:00",
  "action": "delegate",
  "target_agent": "task-orchestrator",
  "context": "Agent handoff detected from prd-research-agent",
  "source_agent": "prd-research-agent",
  "validation_status": "TDD_PASSED"
}

Read the full file on GitHub · 98 lines

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. 2mo ago First seen · 98 lines · 0 tokens per session scan B 24a1aaf358ae

Subscribe to this mod's changes

continue-handoff is a command published in the GitHub repository vanzan01/claude-code-sub-agent-collective (525 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 716 tokens. 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-08-30.

Related

continue-handoff compared with commands from other repositories

continue-handoff next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
continue-handoffvanzan01/claude-code-sub-agent-collectiveCommand5256mo agoMITB0Claude Code
review-pryonatangross/orchestkitCommand299yesterdayMITA40Claude Code, Cursor
fix-issueyonatangross/orchestkitCommand299yesterdayMITA45Claude Code, Cursor
implementyonatangross/orchestkitCommand299yesterdayMITA50Claude Code, Cursor
verifyyonatangross/orchestkitCommand299yesterdayMITA55Claude Code, Cursor
create-pryonatangross/orchestkitCommand299yesterdayMITA46Claude Code, Cursor
design-to-codeyonatangross/orchestkitCommand299yesterdayMITA54Claude Code, Cursor