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.
git clone --depth 1 https://github.com/baodq97/open-pluginWrote 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/baodq97/open-plugin/handoff)<a href="https://agentmods.dev/commands/baodq97/open-plugin/handoff"><img src="https://agentmods.dev/badge/commands/baodq97/open-plugin/handoff/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.
<a href="https://agentmods.dev/commands/baodq97/open-plugin/handoff"><img src="https://agentmods.dev/badge/commands/baodq97/open-plugin/handoff.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00220 |
| Opus 5.5 | $0.00004 | $0.00088 |
| Sonnet 5.5 | $0.00002 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
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 1mo 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
Hand off the completed PRD to the vbounce workflow.
Instructions
- Read
.design-thinking/state.yamlto get the active workspace - Read
{workspace}/state.yamlto get the current state - Validate: PRD phase must be
approved- If not approved, report: "PRD must be approved before handoff. Current status: {status}. Run
/design-thinking:exportfirst."
- If not approved, report: "PRD must be approved before handoff. Current status: {status}. Run
- Copy
{workspace}/prd.mdto the project root asprd.md(or a user-specified path if provided as argument) - 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}/ - Add history entry: "PRD handed off to project root"
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.
- 1mo ago First seen · 26 lines · 11 tokens per session scan A 3c6c4447af14
handoff is a command published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 220 once invoked, about $0.0000 per session on Opus 5.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.
Other commands, from other repositories
business-model
Explore business models using Lean Canvas, Business Model Canvas, Startup Canvas, or Value Proposition frameworks.
brainstorm
Brainstorm product ideas or experiments from PM, Designer, and Engineer perspectives — for existing or new products.
discover
Run a full product discovery cycle — from ideation through assumption mapping to experiment design.
setup-metrics
Design a product metrics dashboard with North Star metric, input metrics, health metrics, and alert thresholds.
triage-requests
Analyze, categorize, and prioritize a batch of feature requests from customers or stakeholders.
pricing
Design a pricing strategy — models, competitive analysis, willingness-to-pay estimation, and pricing experiments.