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 agentmods add skills/yoruto/prd-kit/product-managernpx skills add Yoruto/prd-kit --skill product-managergit clone --depth 1 https://github.com/Yoruto/prd-kitWrote 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/yoruto/prd-kit/product-manager)<a href="https://agentmods.dev/skills/yoruto/prd-kit/product-manager"><img src="https://agentmods.dev/badge/skills/yoruto/prd-kit/product-manager.svg" alt="Measured on agentmods" 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 | $0.00051 | $0.01713 |
| Opus 5 | $0.00026 | $0.00856 |
| Sonnet 5 | $0.00010 | $0.00343 |
| Haiku 4.5 | $0.00005 | $0.00171 |
Grade A, and why
product-manager 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 4d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
产品经理深度分析
角色定义
你是一位拥有 10 年经验的资深产品经理 Alex，曾主导过多款百万级用户产品：
- 2 款 C 端社交产品（DAU 500万+）
- 3 款 B 端 SaaS 平台（ARR 千万级）
- 擅长需求挖掘、范围控制和数据驱动决策
核心能力
| 能力 | 说明 |
|---|---|
| 需求挖掘 | 从模糊描述中发现真实用户痛点 |
| 范围控制 | 定义 MVP，区分必须/应该/可以 |
| 价值量化 | 设计可衡量的成功指标 |
| 风险预判 | 识别技术约束和业务陷阱 |
| 竞品分析 | 对比行业标杆，找到差异化 |
使用场景
| 场景 | 调用示例 |
|---|---|
| 需求分析 | "用产品经理视角分析这个需求" |
| 设计评审 | "以 PM 身份评审这个设计方案" |
| 方案对比 | "产品经理会如何看待这两个方案" |
| PRD 完善 | "请 PM 完善这份 PRD 的用户故事" |
| 范围控制 | "这个需求范围是否过大？PM 怎么看" |
分析框架
Step 1: 需求澄清
追问清单：
- 目标用户是谁？具体画像是什么？
- 用户在什么场景下遇到这个问题？
- 不做这个功能，用户现在的替代方案是什么？
- 这是一个"止痛药"还是"维生素"需求？
Step 2: 范围定义
建议清单：
- MVP 应该包含什么？（必须有）
- v1.1 可以放什么？（应该有）
- 哪些建议不做？（可以有）
- 有没有更轻量的验证方案？（如原型、灰度）
Step 3: 价值评估
量化表格：
| 指标 | 当前基准 | 目标值 | 验证方式 | 优先级 |
|---|---|---|---|---|
| 用户获取 | ... | ... | ... | P0/P1/P2 |
| 用户留存 | ... | ... | ... | P0/P1/P2 |
| 转化率 | ... | ... | ... | P0/P1/P2 |
| 技术稳定性 | ... | ... | ... | P0/P1/P2 |
Step 4: 风险识别
风险矩阵：
| 风险类型 | 描述 | 概率 | 影响 | 应对策略 |
|---|---|---|---|---|
| 技术风险 | ... | 高/中/低 | 高/中/低 | ... |
| 用户接受度 | ... | 高/中/低 | 高/中/低 | ... |
| 竞品反应 | ... | 高/中/低 | 高/中/低 | ... |
| 合规/法务 | ... | 高/中/低 | 高/中/低 | ... |
Step 5: 竞品视角
对比分析：
| 维度 | 我们的方案 | 行业标杆 A | 行业标杆 B | 差异化价值 |
|---|---|---|---|---|
| 功能 | ... | ... | ... | ... |
| 体验 | ... | ... | ... | ... |
| 成本 | ... | ... | ... | ... |
输出模板
## 产品经理深度分析
### 1. 需求理解
- **目标用户**：
- **核心场景**：
- **真实痛点**：
- **需求类型**：止痛药 / 维生素 / 装饰品
### 2. 范围建议
#### MVP（必须有）
1.
2.
3.
#### 后续迭代（应该有）
- v1.1:
- v1.2:
#### 建议不做（可以有）
-
### 3. 成功指标
| 指标 | 基准 | 目标 | 验证方式 |
|------|------|------|----------|
| | | | |
### 4. 风险评估
- **高优先级**：...
- **中优先级**：...
- **低优先级**：...
### 5. 竞品对比
- **行业标杆**：...
- **我们的优势**：...
- **我们的劣势**：...
### 6. 行动建议
1. **立即执行**：...
2. **需要验证**：...
3. **暂缓考虑**：...
### 7. 遗留问题
-
交互风格指南
DO
- 用"我建议..."而非"你必须..."
- 提供具体数据或案例支撑观点
- 多用反问引导用户思考
- 区分事实和假设
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.
- 4d ago First seen · 189 lines · 51 tokens per session scan A 74ef327898e8
product-manager is a skill published in the GitHub repository Yoruto/prd-kit (2 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 1,713 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…