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.
npx skills add BlueprintOS/analysis-to-delivery --skill handoffgit clone --depth 1 https://github.com/BlueprintOS/analysis-to-deliveryWrote 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/skills/blueprintos/analysis-to-delivery/handoff)<a href="https://agentmods.dev/skills/blueprintos/analysis-to-delivery/handoff"><img src="https://agentmods.dev/badge/skills/blueprintos/analysis-to-delivery/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/skills/blueprintos/analysis-to-delivery/handoff"><img src="https://agentmods.dev/badge/skills/blueprintos/analysis-to-delivery/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.00060 | $0.01083 |
| Opus 5 | $0.00030 | $0.00541 |
| Sonnet 5 | $0.00012 | $0.00217 |
| Haiku 4.5 | $0.00006 | $0.00108 |
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 9d 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
Handoff — 代码交接
Contract
- 输入: P0=0 的 QA 审计报告,已完成的全部设计文档,已知风险与待办
- 输出:
HANDOVER.md - 门控: 交接文档含已完成文档清单、待办、风险、后续建议;接收方已确认收到
- Required rules:
stage-gate,doc-numbering,context-pointer,goal-boundary - Required paths:
knowledge-path,tech-stack-path,compliance-path,doc-naming-path - 下一步:
/using-superpowers或交接给开发团队
适用场景
- QA 审计通过(P0=0)
- 准备把设计交付给编码 skill(如
wms-code-implementation)或开发冲刺
流程步骤
1. 整理已完成文档
列出本项目已交付的设计文档:
## 已完成文档
| 编号 | 文档 | 路径 | 状态 |
|---|---|---|---|
| 01 | 业务需求文档 BRD | `01-业务需求文档 BRD.md` | ✅ |
| 02 | 功能规格说明书 FSD | `02-功能规格说明书 FSD.md` | ✅ |
| 03 | 数据模型设计 | `03-数据模型设计.md` | ✅ |
| 04 | 合规评审 | `04-合规评审.md` | ✅ |
| 05 | 产品需求文档 PRD | `05-PRD.md` | ✅ |
| 06 | 开发设计说明书 | `06-开发设计说明书.md` | ✅ |
| 07 | 测试用例设计 | `07-测试用例设计.md` | ✅ |
| 08 | 设计回测报告 | `08-设计回测报告.md` | ✅ |
| 09 | QA 审计报告 | `09-QA审计报告.md` | ✅ |
| - | AGENTS.md | `AGENTS.md` | ✅ |
2. 整理待办事项
按 P0/P1/P2 列出:
## 待办事项
### P0(必须后续处理)
- [ ] ...
### P1(建议后续处理)
- [ ] ...
### P2(可选)
- [ ] ...
3. 整理已知风险与限制
## 已知风险与限制
| 风险 | 影响 | 缓解 | 责任方 |
|---|---|---|---|
| ... | ... | ... | ... |
4. 后续工作建议
- 进入实施:推荐
/using-superpowers走 5 步实施子流程 - 或转交编码 skill:如
wms-code-implementation - 或直接进入开发冲刺:按 PRD §九 上线计划推进
5. 触发
- 转交编码 skill → 在项目根放
HANDOVER.md - 或直接进入开发冲刺 → 把 HANDOVER.md 链接发到团队群
输出
HANDOVER.md
调用的 rule
rules/stage-gate— 阶段 9 门控rules/doc-numbering— HANDOVER 不受编号约束
结束条件
- HANDOVER.md 含 4 节(已完成/待办/风险/后续)
- 接收方(编码 skill / 开发团队)已确认收到
反模式
- ❌ HANDOVER 写"已交付" — 必须含 4 节(已完成/待办/风险/后续),缺一不可
- ❌ 待办事项不给责任方 — 每条 TODO 必须有责任人 + 预期完成时间
- ❌ 已知风险无缓解建议 — 每条风险必须配缓解 + 触发条件
- ❌ 后续工作无优先级 — 必须分 P0/P1/P2,接收方才知道先做什么
- ❌ 不写验收清单(已交付 vs 验收) — 必须含"接收方验收 Checklist" 段
- ❌ HANDOVER 占编号(写 10-HANDOVER) — HANDOVER 不受编号约束,严禁占位
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.
- 9d ago First seen · 109 lines · 60 tokens per session scan A 63b5caf0c55e
handoff is a skill published in the GitHub repository BlueprintOS/analysis-to-delivery (26 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,083 once invoked, about $0.0003 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-30.
Other skills, from other repositories
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
incident-response
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
agb-begriff-vorformuliert-305
Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.