What is generate-handoffs?

A command that creates handoff schemas and validation models for workflows where one AI agent passes work to another.

Use it to generate handoff artifacts for all agents in a plugin or for selected agent-to-agent flows.

It makes the information exchanged between agents explicit and checks that handoffs follow the expected structure.

generate-handoffs — Command for Claude Code by abossenbroek

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/abossenbroek/abossenbroek-claude-plugins

Made for: Claude Code.

Or install context-engineering, the plugin that ships this one along with the rest of its 1 skill, 4 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/abossenbroek/abossenbroek-claude-plugins/generate-handoffs/github.svg)](https://agentmods.dev/commands/abossenbroek/abossenbroek-claude-plugins/generate-handoffs)

Your own site

<a href="https://agentmods.dev/commands/abossenbroek/abossenbroek-claude-plugins/generate-handoffs"><img src="https://agentmods.dev/badge/commands/abossenbroek/abossenbroek-claude-plugins/generate-handoffs/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/abossenbroek/abossenbroek-claude-plugins/generate-handoffs"><img src="https://agentmods.dev/badge/commands/abossenbroek/abossenbroek-claude-plugins/generate-handoffs.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 845 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00845
Opus 5.5	$0.00000	$0.00338
Sonnet 5.5	$0.00000	$0.00169
Haiku 4.5	$0.00000	$0.00085

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

Security

Grade A, and why

generate-handoffs 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.

context-engineering/commands/generate-handoffs.md · 169 lines

How it starts

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

/generate-handoffs Command

Generate handoff schemas and validation models for agent workflows.

Usage

/generate-handoffs [agents]

Arguments

agents (optional):

Comma-separated list of agent file names (default: all agents in current plugin)
Can also specify pairs: agent1->agent2,agent2->agent3

Instructions

You are the MINIMAL entry point for handoff generation. Your ONLY job is to:

Identify agents to generate handoffs for
Launch the handoff-improver directly (no coordinator needed)
Return the generated artifacts directly

Step 1: Identify Agents

If no agents provided:

Look for .claude-plugin/plugin.json in workspace
Extract all agents from manifest
Include coordinator-internal/ agents

If agents provided:

Parse agent names or pairs from argument
Verify files exist

Step 2: Analyze Flows

Use Glob to find agent files:

**/agents/*.md
**/coordinator-internal/**/*.md

Read agent files to identify:

Task tool usage (which agents call which)
Input/output sections
Current handoff patterns

Step 3: Launch Handoff Improver

Use the Task tool to launch the handoff-improver:

Task: Generate handoff schemas
Agent: coordinator-internal/handoff-improver.md
Prompt:
  agent_files:
    - file: [path]
      content: [agent content]
  transitions_to_generate:
    - from: [source agent]
      to: [target agent]
  generate_artifacts: true

The improver will:

Analyze transitions between agents
Determine optimal payloads
Generate YAML handoff schemas
Generate Pydantic models
Generate hook configurations

Step 4: Return Output

Return the generated artifacts DIRECTLY to the user.

Include:

YAML handoff schemas
Pydantic model code
Hook configuration JSON
Implementation notes

DO NOT:

Add commentary about the process
Include intermediate analysis
Modify the artifacts

Examples

/generate-handoffs
# Generates handoffs for all agents in current plugin

/generate-handoffs coordinator,analyzer,validator
# Generates handoffs between specified agents

/generate-handoffs coordinator->analyzer,analyzer->validator
# Generates handoffs for specific transitions

Read the full file on GitHub · 169 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.

2mo ago First seen · 169 lines · 0 tokens per session scan A a0c2d5b6a130

Subscribe to this mod's changes

generate-handoffs is a command published in the GitHub repository abossenbroek/abossenbroek-claude-plugins (2 stars, last pushed 6mo ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 845 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-31.

Building agents

generate-handoffs next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
generate-handoffsabossenbroek/abossenbroek-claude-plugins	Command	2	6mo ago	BSD-3-Clause	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
convergegithub/spec-kit	Command	148k	today	MIT	A	35	Claude Code
speckit.bug.testgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	today	MIT	A	26	Claude Code