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/test-handoff-chaingit 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/test-handoff-chain)<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="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.1 | $0.00000 | $0.00379 |
| Opus 5 | $0.00000 | $0.00189 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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 6d 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
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:
- Start: mock-test-handoff-agent (reads tasks, initiates chain)
- Infrastructure: mock-implementation-agent (Task 1 setup)
- Component: mock-component-implementation-agent (Task 2 TodoList)
- Testing: mock-testing-agent (Task 4 Jest tests)
- Complete: Full validation evidence
Expected Evidence
After running, you should see:
.claude/handoff/NEXT_ACTION.jsonfiles 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
- Context Files: Check
.claude/handoff/for NEXT_ACTION.json - Hook Logs: Review
/tmp/test-driven-handoff.logfor detections - Auto-Delegation: Verify no manual intervention needed
- 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.
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.
- 6d ago First seen · 52 lines · 0 tokens per session scan A e35976e90669
test-handoff-chain 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 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.
Other commands, from other repositories
design-import
Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship…
dev
One-command dev loop boot. Spins up portless (named HTTPS subdomain), emulate (stateful API mocks), the project's dev server, and an agent-browser session, all keyed to the current git branch. Use when starting a feature branch, switching worktrees, or returning to a project after a break. Skips silently with install…
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
paul:verify
Guide manual user acceptance testing of recently built features.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
generate-widget
Génération Widget Flutter avec Tests.