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/reset-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/reset-handoff)<a href="https://agentmods.dev/commands/vanzan01/claude-code-sub-agent-collective/reset-handoff"><img src="https://agentmods.dev/badge/commands/vanzan01/claude-code-sub-agent-collective/reset-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.00402 |
| Opus 5 | $0.00000 | $0.00201 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
reset-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.
What it actually says
Reset Agent Handoff Workflow
Reset the agent handoff system by cleaning up state files and logs.
What This Does
Clears all handoff-related state files so you can start a fresh agent workflow:
- Removes
.claude/handoff/NEXT_ACTION.json(pending delegation context) - Clears handoff logs in
/tmp/test-driven-handoff.log - Resets any stuck delegation state
- Prepares for clean workflow restart
Usage
# Remove handoff context files
rm -f .claude/handoff/NEXT_ACTION.json
# Clear handoff logs
> /tmp/test-driven-handoff.log
# Optional: Clear any other temp handoff files
rm -f .claude/handoff/*.json
When to Use
- Stuck Handoffs: When delegation gets stuck or loops
- Fresh Start: Before beginning new agent workflow
- Testing: Between test runs to ensure clean state
- Debugging: When investigating handoff issues
Files Cleaned
.claude/handoff/NEXT_ACTION.json- Current delegation context/tmp/test-driven-handoff.log- Hook execution logs.claude/handoff/*.json- Any other handoff state files
Safe Operation
This only removes temporary state files, never:
- TaskMaster data (
.taskmaster/tasks/) - Agent definitions (
.claude/agents/) - Hook scripts (
.claude/hooks/) - Project files or code
Verification
After reset, verify clean state:
ls .claude/handoff/ # Should be empty or not exist
tail /tmp/test-driven-handoff.log # Should be empty
Quick one-liner for complete reset:
rm -f .claude/handoff/*.json && > /tmp/test-driven-handoff.log && echo "Handoff workflow reset complete"
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 · 59 lines · 0 tokens per session scan A f0211ce0bfd4
reset-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 402 tokens. 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 commands, from other repositories
remember
Stores decisions, patterns, and outcomes in the MCP memory knowledge graph as entities with typed observations and relations. Supports recording architectural decisions, anti-patterns, tool preferences, workflow outcomes, and project conventions that persist across sessions. Use when saving patterns, remembering…
memory
Unified read-side memory operations including knowledge graph search, session context loading, decision timeline viewing, and Mermaid graph visualization. Subcommands: search, load, history, viz, status. Complements /ork:remember (write-side). Use when searching past decisions, loading context, or visualizing the…
paul:resume
Restore context from handoff and continue work.
dream
Nightly memory consolidation — prunes stale entries, merges duplicates, resolves contradictions, rebuilds MEMORY.md index. Use when memory files have accumulated over many sessions and need cleanup. Do NOT use for storing new decisions (use remember) or searching memory (use memory).
context-health
Dashboard de salud del contexto activo con predicción de degradación y recomendaciones de compactación. Usa cuando el usuario dice "context health", "salud del contexto", "degradation", "compactar contexto", "context overflow", "tokens", "session health", "compact", "contexto lleno". Monitorea degrdación del contexto…
capturar
Capturar ideas y notas sin interrumpir el flujo de trabajo. Usa cuando el usuario dice "capturar idea", "quick note", "nota rápida", "grab this", "take a note", "guardar idea", "note to self", "capture thought", "I should remember", "guardar esto". Guarda en memoria persistente sin romper el contexto actual.