handoff

A command that prepares a detailed briefing so another developer can continue an ongoing research sprint. It reads project instructions, current findings, the full claim history, and the Git log.

In plain words
What is it for?
Use it when transferring work to a successor or resuming a research sprint. It helps summarize the reasoning, evidence, conflicts, and open questions.
Why use it?
It reduces the time needed to understand what has already happened, why decisions were made, and what remains unresolved.

Command

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.

agentmods
npx agentmods add commands/grainulation/wheat/handoff
Clone the repo
git clone --depth 1 https://github.com/grainulation/wheat
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 450 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00450
Opus 5 $0.00000 $0.00225
Sonnet 5 $0.00000 $0.00090
Haiku 4.5 $0.00000 $0.00045

Measured yesterday against content hash cdd567b02134, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 yesterday.

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/handoff.md · 58 lines

What it actually says

/handoff — Package Sprint for Transfer

You are generating a self-contained briefing optimized for a successor — someone who needs to continue this sprint, not a stakeholder making a decision. Read CLAUDE.md, claims.json, and compilation.json.

Key distinction from other output commands

Command Audience Optimized for
/brief Decision-makers "What should we do?"
/present External audiences Persuasion
/status Current researcher Snapshot
/handoff Successor "What do I need to know to continue?"

Process

  1. Run the compiler:

    npx @grainulation/wheat compile --summary
    
  2. Read all data sources:

    • compilation.json — current state
    • claims.json — all claims including superseded ones (the full history)
    • git log --oneline claims.json — the event log
    • CLAUDE.md — sprint context and conventions
  3. Build the reasoning chain: For each topic, reconstruct the narrative:

    • What constraint or question initiated work on this topic?
    • What did research find?
    • Did prototyping confirm or contradict research?
    • Were there conflicts? How were they resolved?
  4. Identify open questions: From compilation.json:

    • Unresolved conflicts
    • Coverage gaps
    • Unmitigated risks
    • Dismissed blind spots
  5. Generate the handoff document: Create output/handoff.md and output/handoff.html.

  6. Print a summary to the terminal.

Git commit

Commit: wheat: /handoff — generated sprint handoff document

Tell the user

  • Point them to output/handoff.md and output/handoff.html
  • Highlight the most important open questions
  • Suggest: /replay for detailed timeline, /blind-spot for gap analysis

$ARGUMENTS

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. yesterday First seen · 58 lines · 0 tokens per session scan A cdd567b02134

Subscribe to this mod's changes

handoff is a command published in the GitHub repository grainulation/wheat (20 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 450 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.