handoff

A command that creates a structured handoff document describing a coding session’s status, decisions, files, risks, and next steps.

In plain words
What is it for?
Use it when handing work to someone else or starting a later session, including recording specification status, build results, changed files, and pending actions.
Why use it?
It gives another session or developer enough context to continue work without reconstructing the entire conversation.

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/zhmxiaowo/opencode-simple/handoff
Clone the repo
git clone --depth 1 https://github.com/zhmxiaowo/opencode-simple
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 590 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.00027 $0.00590
Opus 5 $0.00014 $0.00295
Sonnet 5 $0.00005 $0.00118
Haiku 4.5 $0.00003 $0.00059

Measured yesterday against content hash bd7a3b1aeb09, 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.

.opencode/commands/handoff.md · 69 lines

What it actually says

/handoff — 会话交接

生成一份结构化的交接文档,包含当前工作的完整上下文,使另一个 session(或未来的你)可以立即继续工作。

输出格式

# Handoff: [当前任务简述]

**Date:** YYYY-MM-DD
**Branch:** [当前分支]

## 1. 当前状态
- [ ] 已完成的步骤
- [x] 正在进行的步骤
- [ ] 待完成的步骤

## 2. SPEC 状态
- SPEC 位置: [文件路径,如果有]
- SPEC 状态: DRAFT / CONFIRMED / IMPLEMENTING / DONE
- 关键设计决策: [列出]

## 3. CDD 状态
- 编译命令: [具体命令]
- 上次编译结果: PASS / FAIL
- 未解决的编译错误: [如果有,列出]
- sequential-thinking 分析结论: [如果有]

## 4. 文件变更清单
[git diff --name-only HEAD 的输出]

## 5. 关键决策记录
- [决策 1]: [原因]
- [决策 2]: [原因]

## 6. 已知风险 / 阻塞项
- [风险/阻塞 1]

## 7. 下一步行动
1. [具体的下一步]
2. [具体的下一步]

工作流程

  1. 收集状态 — 读取 git status、当前分支、SPEC 文件、最近的编译结果
  2. 总结决策 — 回顾本次会话做出的关键技术决策和原因
  3. 输出文档 — 生成到 docs/handoff-YYYY-MM-DD.md 或直接输出到对话
  4. 存入 memory — 调用 memory MCP 持久化交接摘要

与 /save-session 的区别

/save-session /handoff
粒度 自动快照 结构化、人类可读
CDD 状态 ✅ 编译命令 + 结果
SPEC 状态 ✅ 位置 + 进度
决策记录 ✅ 关键决策 + 原因
下一步行动 ✅ 具体可执行

参数

  • /handoff — 完整交接文档
  • /handoff brief — 简要版(只输出状态 + 下一步)
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 · 69 lines · 27 tokens per session scan A bd7a3b1aeb09

Subscribe to this mod's changes

handoff is a command published in the GitHub repository zhmxiaowo/opencode-simple (2 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 590 once invoked, about $0.0001 per session on Opus 5. 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.