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 commands/vanzan01/claude-code-sub-agent-collective/continue-handoffgit clone --depth 1 https://github.com/vanzan01/claude-code-sub-agent-collectiveWrote 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/commands/vanzan01/claude-code-sub-agent-collective/continue-handoff)<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="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.00000 | $0.00716 |
| Opus 5 | $0.00000 | $0.00358 |
| Sonnet 5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00072 |
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 4d 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 '.' 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.jsonfor 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"
}
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.
- 4d ago First seen · 98 lines · 0 tokens per session scan B 24a1aaf358ae
continue-handoff is a command published in the GitHub repository vanzan01/claude-code-sub-agent-collective (521 stars, last pushed 4mo 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.
Other commands, from other repositories
paul:help
Show available PAUL commands and usage guide.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
paul:verify
Guide manual user acceptance testing of recently built features.
paul:discover
Research technical options before planning a phase.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
adr
You are helping create a new ADR (Architecture Decision Record). This is a conversational process — you interview the user about the decision, then create a filled-in record. ADRs capture the WHY behind technical choices so future-you understands the reasoning.