agentmods.dev

test-handoff-chain

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

A command for testing an automated workflow in which coding agents pass work and context from one agent to another.

In plain words
What is it for?
Use it to test a four-stage mock workflow covering setup, component implementation, Jest tests, and final validation.
Why use it?
It checks whether handoffs, task tracking, context files, and validation steps work across a complete development sequence.

Command for Claude Code

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

not rated 525repo +3 6mo ago A scan 0 tokens original MIT

Good fit Use it to test a four-stage mock workflow covering setup, component implementation, Jest tests, and final validation.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/vanzan01/claude-code-sub-agent-collective/test-handoff-chain
View source ↗ vanzan01/claude-code-sub-agent-collective
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 test-handoff-chain

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/vanzan01/claude-code-sub-agent-collective/test-handoff-chain"><img src="https://agentmods.dev/badge/commands/vanzan01/claude-code-sub-agent-collective/test-handoff-chain.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 379 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.00000 $0.00379
Opus 5.5 $0.00000 $0.00152
Sonnet 5.5 $0.00000 $0.00076
Haiku 4.5 $0.00000 $0.00038

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

Security

Grade A, and why

test-handoff-chain 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 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.

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.

templates/commands/test-handoff-chain.md · 52 lines

What it actually says

Test Handoff Chain

Test the complete handoff automation mechanism using mock agents with real TaskMaster tasks.

What This Tests

  • DECISION.md auto-delegation mechanism
  • NEXT_ACTION.json context file creation
  • Hook-based handoff detection
  • Context reconstruction protocol
  • TaskMaster integration with handoffs

Test Scenario

Simulates the complete development workflow:

  1. Start: mock-test-handoff-agent (reads tasks, initiates chain)
  2. Infrastructure: mock-implementation-agent (Task 1 setup)
  3. Component: mock-component-implementation-agent (Task 2 TodoList)
  4. Testing: mock-testing-agent (Task 4 Jest tests)
  5. Complete: Full validation evidence

Expected Evidence

After running, you should see:

  • .claude/handoff/NEXT_ACTION.json files created at each step
  • Hook logs showing handoff detection
  • Automatic delegation without manual intervention
  • Complete chain execution through all 4 agents

Usage

# In Claude Code:
Use the mock-test-handoff-agent subagent to validate the complete handoff automation chain.

Validation Points

  1. Context Files: Check .claude/handoff/ for NEXT_ACTION.json
  2. Hook Logs: Review /tmp/test-driven-handoff.log for detections
  3. Auto-Delegation: Verify no manual intervention needed
  4. Chain Completion: All 4 agents execute in sequence

Success Criteria

✅ Each agent creates proper handoff syntax
✅ Hook detects patterns and creates context files
✅ Auto-delegation triggers correctly
✅ Full chain completes without interruption
✅ Real TaskMaster tasks used (not mock data)

This validates that our handoff mechanism works in cleared contexts and with real project data.

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 · 52 lines · 0 tokens per session scan A e35976e90669

Subscribe to this mod's changes

test-handoff-chain 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 379 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.

Building agentsClaude CodeTestingagentsai-developmentclaudetaskmasteryolo
Related

test-handoff-chain compared with commands from other repositories

test-handoff-chain next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
test-handoff-chainvanzan01/claude-code-sub-agent-collectiveCommand5256mo agoMITA0Claude 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