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 yike-gunshi/forge-skills --skill forge-prdgit clone --depth 1 https://github.com/yike-gunshi/forge-skillsWrote 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/yike-gunshi/forge-skills/forge-prd)<a href="https://agentmods.dev/skills/yike-gunshi/forge-skills/forge-prd"><img src="https://agentmods.dev/badge/skills/yike-gunshi/forge-skills/forge-prd/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/yike-gunshi/forge-skills/forge-prd"><img src="https://agentmods.dev/badge/skills/yike-gunshi/forge-skills/forge-prd.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.00097 | $0.04403 |
| Opus 5 | $0.00048 | $0.02201 |
| Sonnet 5 | $0.00019 | $0.00881 |
| Haiku 4.5 | $0.00010 | $0.00440 |
Grade A, and why
forge-prd 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 11d 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
文档落地路径：遵循 forge-doc-policy 规范。完整白名单 + frontmatter schema 见
~/.claude/skills/forge-doc-policy/doc-paths.md。 当前文档加载契约：先读项目CLAUDE.md、docs/README.md、docs/INDEX.md和根级当前真相源；长 changelog 和 raw archive 只在追溯历史原因时加载。详见~/.claude/skills/_shared/current-doc-loading.md。
/forge-prd：产品诊断与 PRD 迭代管理器
流程总览
全程中文。每个步骤结束后暂停等待用户反馈。
用户描述问题/需求
│
▼
┌─ 第0步：定位 ──────────────────────────┐
│ Glob 搜索 PRD / CHANGELOG │
│ ├─ 找到 PRD → 迭代模式 │
│ ├─ 没找到 → [询问用户] 是否创建模式 │
│ └─ 没找到 CHANGELOG → 标记第4步新建 │
└──────────────────────────────────────────┘
│
▼
┌─ 第1步：理解现状 ─────────────────────────┐
│ 读 PRD + CHANGELOG + Agent(Explore)源码 │
│ 热点分析（模块修改频次） │
│ → [询问用户] 总结现状，确认理解是否正确 │
│ → [询问用户] 本次迭代需求是什么？ │
└─────────────────────────────────────────────┘
│
▼
┌─ 第2步：诊断与审查 ──────────────────────────┐
│ 自动判定层级：轻量 / 标准 / 深度 │
│ ┌─ 所有层级 ─────────────────────────┐ │
│ │ ① 问题归因（设计缺陷/偏离/遗漏） │ │
│ │ ② 10星挑战（当前几星→10星差距） │ │
│ └─────────────────────────────────────┘ │
│ ┌─ 标准+深度 ─────────────────────────┐ │
│ │ ③ 模块健康度检查 │ │
│ └─────────────────────────────────────┘ │
│ ┌─ 仅深度 ───────────────────────────┐ │
│ │ ④ 假设审查 ⑤ 反驳机制 │ │
│ └─────────────────────────────────────┘ │
│ → [询问用户] 展示诊断结果，确认方向 │
└───────────────────────────────────────────────┘
│
▼
┌─ 第3步：方案确认 ─────────────────────────────┐
│ 逐项讨论变更点（当前→目标→推荐→可选） │
│ → [多轮询问用户] 每个变更点确认 │
│ → [询问用户] 汇总变更清单，最终确认 │
│ ⚠️ 门禁：确认前不写任何文件 │
└────────────────────────────────────────────────┘
│ 用户确认 ✓
▼
┌─ 第4步：写入文档 ─────────────────────────────┐
│ A. 更新/新建 Feature Spec（.features） │
│ B. 将最终有效结论回写 PRD 当前事实 │
│ C. 更新 CHANGELOG 历史账本 │
│ → 输出最终总结 │
└────────────────────────────────────────────────┘
What ships with it
4 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.
- 11d ago First seen · 333 lines · 97 tokens per session scan A 40a39dfd8447
forge-prd is a skill published in the GitHub repository yike-gunshi/forge-skills (13 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 4,403 once invoked, about $0.0005 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
vastai
Vast.ai CLI to manage GPU instances, volumes, serverless endpoints, and billing.
vastai-sdk
Vast.ai Python SDK — high-level API for GPU instances, volumes, serverless endpoints, and billing.
forge-evolution
Autonomous persona evolution pipeline for failure-driven capability growth.
docs-context
Super Base Context — project doc loader & synchronizer. Triggers even without explicit "load docs"/"sync docs." READ MODE — load architecture/modules/coding/decision docs when work references project state: code work (write/modify/remove); design (features/APIs/schemas/architecture); review (modules, past solutions)…
houtu-dependencies
Skill "houtu-dependencies" from lujiafa/houtu-project-skills, covering houtu framework — ai agent coding guide, core principles, code generation workflow (must be executed in order), step 1 — detect version & dependencies and step 2 — identify scenario & select module.
senzing-entity-resolution
Guides AI agents through Senzing entity resolution workflows using the Senzing MCP server. Covers data mapping to Senzing format, SDK code generation (Python, Java, C#, Rust, TypeScript/Node.js), documentation search, error troubleshooting, sample data access, reporting and visualization, SDK setup guides, and…