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 mileson/openprd --skill openprd-diagram-reviewgit clone --depth 1 https://github.com/mileson/openprdWrote 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/mileson/openprd/openprd-diagram-review)<a href="https://agentmods.dev/skills/mileson/openprd/openprd-diagram-review"><img src="https://agentmods.dev/badge/skills/mileson/openprd/openprd-diagram-review/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/mileson/openprd/openprd-diagram-review"><img src="https://agentmods.dev/badge/skills/mileson/openprd/openprd-diagram-review.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.00066 | $0.01478 |
| Opus 5 | $0.00033 | $0.00739 |
| Sonnet 5 | $0.00013 | $0.00296 |
| Haiku 4.5 | $0.00007 | $0.00148 |
Grade A, and why
openprd-diagram-review 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 6d 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.
This is a copy
91% identical to openprd-diagram-review — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenPrd Diagram Review
概览
这份 skill 用来判断当前需要哪种图：轻量解释图、正式 diagram contract，或需要用户往返确认的评审循环。不要把所有图都当成 freeze 前评审图；很多时候用户只是需要先看懂问题。
动手前
- 读取
skills/openprd-shared/SKILL.md - 重建当前工作区状态，判断用户究竟想确认什么
- 决定用户需要的是：
explanation-svg轻量解释图architecture视图product-flow视图
- 不要虚构今天还不存在的 OpenPrd diagram 命令
图示类型选择
当用户在问这些内容时，优先选 explanation-svg：
- 为什么会这样
- 这两个方案差在哪里
- 当前状态怎么走到目标状态
- 过去、现在、未来的关系
- 因果、依赖、边界、风险传播
- Agent 要向用户解释需求场景、问题结构、决策取舍或下一步路径
explanation-svg 是对话辅助。它可以用内联 SVG、HTML 片段或 Markdown 中的 SVG 代码块表达；它不需要写入 .openprd/engagements/active/，也不替代 openprd diagram、review.html、visual-compare 或测试证据。
当用户在问这些内容时，选 architecture：
- 模块
- 系统边界
- 服务
- 外部依赖
- 可靠性 / 合规性问题
- handoff 形态
当用户在问这些内容时，选 product-flow：
- 用户步骤
- 决策点
- 正常路径 / 错误路径
- onboarding 或旅程流程
- 页面到页面、步骤到步骤的推进
如果两者都出现：
- 当用户行为和流程仍不清楚时，先做
product-flowcontract - 流程清楚后，再做架构评审
- 如果只是为了让用户先理解取舍，不进入定稿评审，先给
explanation-svg
解释型 SVG 规则
- 输出顺序优先是：一句结论、SVG 图、最多 3 条补充说明或开放问题。
- 图中每个节点只放短标签和 1 行例子；正文解释放到图下，不要把 SVG 变成文字墙截图。
- 优先使用 2 到 5 个节点、明确箭头、颜色分组、虚线边界、少量图例；避免复杂渐变、装饰背景和难读小字。
- 适合的图形包括：双栏对比、时间线、状态转移、边界/责任图、决策树、风险传播、因果反推。
- 图中用户可见文案跟随用户当前主语言；中文语境用简体中文，专有名词可保留，但不要在中文语境下整句英文。
- 如果没有足够事实支撑图中的节点或箭头，先把缺口写成“待确认”，不要把推测画成事实。
- 需要模板时读取
references/explanation-svg-patterns.md。
当前工具能力
当前 OpenPrd CLI 提供：
openprd diagram <path> [--open] [--json]
现在它主要渲染面向架构的 HTML / JSON 产物。
因此：
- 对
explanation-svg，直接在对话或临时 HTML/SVG artifact 中生成轻量图，不声称已进入正式 diagram 评审 - 对
architecture，直接调用内置命令 - 对
product-flow，即使还没有专门渲染器，也先生成结构化 contract 和评审清单 - 如果工具还没有专用流程渲染器，就不要假装它已经存在
语言规则
- 所有用户可见标签和评审说明都跟随用户当前主语言
- Diagram contract 是用户可见产物。当
locale为zh-CN时，以下可见字段必须写成简体中文：title、subtitlecomponents[].name、components[].subtitle、components[].detailsflows[].labelsummaryCards[].title、summaryCards[].itemssidePanels[].title、sidePanels[].itemsreviewInstructions
- 专有名词、产品名、协议名、API 名称、框架名和云服务名在翻译会降低清晰度时保持原样
- 像 MotiClaw、Electron、TypeScript、CLI、API、JSON、NDJSON、dry-run、Host API、schema、
waiting_approval这类必要术语可以保留，但周围句子必须译成简体中文 - 不要在 zh-CN diagram contract 里写完整英文句子。运行
openprd diagram --input前，至少人工检查一遍并把英文偏重的可见文本改成简体中文 - 如果对话语言混合，优先跟随最近几轮需求澄清中占主导的语言
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 117 lines · 66 tokens per session scan A 2ea6c1b649c6
openprd-diagram-review is a skill published in the GitHub repository mileson/openprd (50 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 1,478 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to openprd-diagram-review, differing in 13 lines, and is treated as a copy.
Other skills, from other repositories
openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-ff-change
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.