handoff

A command that transfers an approved product requirements document, or PRD, from a Design Thinking session into the project root. A PRD describes what a product should do and why.

In plain words
What is it for?
Use it after the PRD phase is approved to copy the PRD as prd.md and start the vbounce software-development workflow.
Why use it?
It gives the next development workflow a known location for the approved requirements.

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/baodq97/open-plugin/handoff
Clone the repo
git clone --depth 1 https://github.com/baodq97/open-plugin
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 220 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.00011 $0.00220
Opus 5 $0.00005 $0.00110
Sonnet 5 $0.00002 $0.00044
Haiku 4.5 $0.00001 $0.00022

Measured 2d ago against content hash 3c6c4447af14, 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 2d 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.

plugins/design-thinking/commands/handoff.md · 26 lines

What it actually says

Hand off the completed PRD to the vbounce workflow.

Instructions

  1. Read .design-thinking/state.yaml to get the active workspace
  2. Read {workspace}/state.yaml to get the current state
  3. Validate: PRD phase must be approved
    • If not approved, report: "PRD must be approved before handoff. Current status: {status}. Run /design-thinking:export first."
  4. Copy {workspace}/prd.md to the project root as prd.md (or a user-specified path if provided as argument)
  5. Report:
    PRD copied to ./prd.md
    
    To start the vbounce SDLC cycle with this PRD:
      /vbounce:start prd.md
    
    Design Thinking session: {session_id}
    Artifacts preserved at: {workspace}/
    
  6. Add history entry: "PRD handed off to project root"
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. 2d ago First seen · 26 lines · 11 tokens per session scan A 3c6c4447af14

Subscribe to this mod's changes

handoff is a command published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 220 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.