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 kelegele/oh-my-pm --skill prd-gengit clone --depth 1 https://github.com/kelegele/oh-my-pmWrote 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/kelegele/oh-my-pm/prd-gen)<a href="https://agentmods.dev/skills/kelegele/oh-my-pm/prd-gen"><img src="https://agentmods.dev/badge/skills/kelegele/oh-my-pm/prd-gen/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/kelegele/oh-my-pm/prd-gen"><img src="https://agentmods.dev/badge/skills/kelegele/oh-my-pm/prd-gen.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.00115 | $0.05832 |
| Opus 5 | $0.00057 | $0.02916 |
| Sonnet 5 | $0.00023 | $0.01166 |
| Haiku 4.5 | $0.00012 | $0.00583 |
Grade A, and why
prd-gen 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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Generation
Generate structured Product Requirements Documents from feature ideas.
What This Skill Does
Transforms informal feature requests into complete PRDs with user stories, acceptance criteria, functional requirements, success metrics, and compliance guidance. The output is ready for engineering teams to implement and stakeholders to review.
When to Use
Activate this skill when:
- User wants to document a new feature or product idea
- Phrases like "write a PRD", "create requirements", "document this feature"
- Preparing for product review, stakeholder alignment, or engineering handoff
- User mentions user stories, acceptance criteria, or success metrics
- Need to formalize a rough idea into structured documentation
Scenario Detection (CRITICAL - First Step)
Before generating any PRD content, you MUST identify the scenario.
Ask the user which scenario applies (use the host's structured-question tool if available, e.g. AskUserQuestion on Claude Code; otherwise present a numbered option list and wait for the reply):
Q: 请选择 PRD 生成场景
| Option | Description |
|---|---|
| 迭代更新 | 基于现有功能进行迭代优化 |
| 新功能 | 在现有产品上添加新模块 |
| 0-1 新产品 | 从零开始规划全新产品 |
Context Collection by Scenario
Once scenario is identified, collect required context:
| Scenario | Required Information | Collection Method |
|---|---|---|
| 迭代更新 | 1. 当前功能描述2. UI 状态（截图/HTML/链接）3. 迭代目标 | User input + structured question for UI state option |
| 新功能 | 1. 产品整体架构2. 设计规范（组件库/交互模式）3. 入口位置 | Read from docs/product/ or user input |
| 0-1 新产品 | 1. 产品背景与目标用户2. 资源约束3. 参考产品 | User input + competitive analysis |
UI State Collection for Iteration Updates: When user selects "迭代更新", ask how they want to provide current UI state:
- 截图 - User provides screenshot; read it with the host's image-understanding capability (on Claude Code, e.g.
mcp__4_5v_mcp__analyze_image/mcp__zai-mcp-server__ui_to_artifactMCP tools; other hosts use their built-in image reading) - HTML 文件 - User provides local HTML path, use
Readtool to parse DOM structure - 在线链接 - User provides URL; read it with the host's web-reading capability (on Claude Code, e.g.
mcp__web_reader__webReader; other hosts use their built-in web access) (no login required)
What ships with it
3 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 · 376 lines · 115 tokens per session scan A 045279b446c2
prd-gen is a skill published in the GitHub repository kelegele/oh-my-pm (4 stars, last pushed 1mo ago), licensed MIT. It adds 115 tokens to every session and 5,832 once invoked, about $0.0006 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-31.
Other skills, from other repositories
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.