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-experience-quality-candidate-eval-20260620185705git 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-experience-quality-candidate-eval-20260620185705)<a href="https://agentmods.dev/skills/mileson/openprd/openprd-experience-quality-candidate-eval-20260620185705"><img src="https://agentmods.dev/badge/skills/mileson/openprd/openprd-experience-quality-candidate-eval-20260620185705/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-experience-quality-candidate-eval-20260620185705"><img src="https://agentmods.dev/badge/skills/mileson/openprd/openprd-experience-quality-candidate-eval-20260620185705.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.00997 |
| Opus 5 | $0.00018 | $0.00498 |
| Sonnet 5 | $0.00007 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
openprd-experience-quality-candidate-eval-20260620185705 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
openprd-experience-quality-candidate-eval-20260620185705
状态:draft 候选目录:
.openprd/knowledge/candidates/candidate-eval-20260620185705Promote:openprd quality . --learn --from .openprd/knowledge/candidates/candidate-eval-20260620185705
触发条件
- doctor-green: doctor passed
- dev-check: dev-check attention=0, warning=1 | touched: src/canvas-app.html.js, src/canvas-i18n.js, test/openprd-canvas.test.js
- dev-check: dev-check attention=1, warning=0 | touched: src/canvas-app.html.js, test/openprd-canvas.test.js
- dev-check: dev-check attention=2, warning=2 | touched: src/canvas-app.html.js, src/canvas-workspace.js, src/cli/args.js, src/cli/canvas-print.js, src/openprd.js, src/agent-integration.js
- dev-check: dev-check attention=2, warning=0 | touched: src/canvas-app.html.js, src/canvas-i18n.js, src/canvas-workspace.js, test/openprd-canvas.test.js
- dev-check: dev-check attention=3, warning=1 | touched: src/canvas-workspace.js, src/canvas-app.html.js, src/canvas-i18n.js, src/agent-integration.js, test/openprd-canvas.test.js, test/openprd-agent-integration.test.js
- dev-check: dev-check attention=2, warning=0 | touched: src/canvas-app.html.js, src/canvas-workspace.js, src/canvas-i18n.js, test/openprd-canvas.test.js
- dev-check: dev-check attention=2, warning=2 | touched: src/canvas-workspace.js, src/canvas-app.html.js, src/cli/canvas-print.js, src/cli/args.js, src/cli/print.js, src/openprd.js
适用范围
- 抽象模式: 质量缺口反复出现,通常是因为可观测性、护栏、测试与复盘知识被分散维护,没有进入同一套项目级诊断闭环。
- 适用于项目源码或核心流程已经落地、需要把实现经验固化为项目知识的任务。
- 适用于本轮补过验证或测试夹具,后续同类需求需要同步复用验证方式的任务。
典型输入
- 任务场景: 质量门禁收口
- 相关文件: src/canvas-app.html.js、src/canvas-i18n.js、test/openprd-canvas.test.js
- 已有证据类型: quality-report
- 验证信号: doctor-green、dev-check
典型输出
- 项目经验候选与诊断包
- 待确认的项目经验草案
- 验证结论: doctor passed
- 可复用的验证链路与收尾动作
下次触发时先看什么
src/canvas-app.html.jssrc/canvas-i18n.jstest/openprd-canvas.test.js.openprd/quality/reports/eval-20260620185705.json
不要直接套用
- 如果只是文件名、路径或个别词相似,但当前目标和验证方式不同,不要直接套用。
- 如果当前任务还没进入验证或收尾阶段,不要把这条经验当成通用实现模板。
- 如果本轮已经有更新的现场证据,先核对新证据,再决定是否复用旧经验。
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.
- 12d ago First seen · 71 lines · 36 tokens per session scan A f299bd362f72
openprd-experience-quality-candidate-eval-20260620185705 is a skill published in the GitHub repository mileson/openprd (50 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 997 once invoked, about $0.0002 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
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-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.