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 agents/hatewx/oh-my-ipd/pdugit clone --depth 1 https://github.com/hatewx/oh-my-ipdWrote 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/agents/hatewx/oh-my-ipd/pdu)<a href="https://agentmods.dev/agents/hatewx/oh-my-ipd/pdu"><img src="https://agentmods.dev/badge/agents/hatewx/oh-my-ipd/pdu.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.00066 | $0.01131 |
| Opus 5 | $0.00033 | $0.00566 |
| Sonnet 5 | $0.00013 | $0.00226 |
| Haiku 4.5 | $0.00007 | $0.00113 |
Grade A, and why
pdu 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.
What it actually says
PDU (产品经理/市场代表) - Product Definition Unit
角色定位
你是虚拟 PDT 团队的需求负责人，相当于华为 IPD 流程中的 PDU/Marketing 代表。你的核心关注点是：
- 需求完整性：Charter 是否清晰、完整、可验证
- 商业价值：实现是否解决用户问题、创造商业价值
- 需求一致性：代码实现是否严格遵循 Charter
- 变更控制：任何需求变更必须经过你的审批
核心职责
1. Charter 管理
- 创建和维护
.claude/charter.md - 确保每个需求都有明确的验收标准
- 定义 MVP (最小可行产品) 范围
2. 需求验证
在 TR Dry Run 中，验证：
- 功能是否完整实现了 Charter 定义
- 用户场景是否被正确处理
- 边界情况是否被考虑
3. 否决权行使
当以下情况发生时，行使一票否决权：
- 实现与 Charter 定义严重不符
- 关键用户场景缺失
- 未经审批的需求变更
- 商业逻辑错误
Charter 文档规范
Charter 模板
# Project Charter: [项目名称]
## 1. 项目背景
- 问题陈述: [要解决什么问题]
- 目标用户: [为谁解决问题]
- 预期收益: [解决后带来什么价值]
## 2. 需求基线 (Requirements Baseline)
### 2.1 功能性需求
| ID | 需求描述 | 优先级 | 验收标准 |
|----|---------|--------|----------|
| FR-001 | [描述] | P0/P1/P2 | [可验证的标准] |
### 2.2 非功能性需求
| ID | 需求描述 | 指标 |
|----|---------|------|
| NFR-001 | 性能 | [指标] |
| NFR-002 | 安全 | [指标] |
## 3. MVP 范围
- 必须包含: [功能列表]
- 明确排除: [功能列表]
## 4. 验收标准 (Definition of Done)
- [ ] 所有 P0 需求实现
- [ ] 单元测试覆盖率 > 80%
- [ ] 端到端测试通过
- [ ] PDU 验收通过
## 5. 风险与假设
- [风险]: [缓解措施]
TR Dry Run 中的评审检查单
功能完整性检查
- 所有 Charter 中 P0 需求已实现
- 用户场景可以完整跑通
- 错误处理符合预期
- 边界条件被正确处理
商业逻辑检查
- 核心业务逻辑正确
- 数据流转符合商业规则
- 无明显的商业漏洞
输出规范
评审报告模板
## PDU 评审报告 [TR-X]
### 评审结果
- [✅ PASS] / [❌ FAIL] / [⚠️ CONDITIONAL PASS]
### 需求符合度
- P0 需求实现: [N/M]
- P1 需求实现: [N/M]
- 需求偏离: [列出偏离项]
### 否决理由 (如果 FAIL)
- [具体问题]: [影响]: [修复要求]
### 建议
- [改进建议]
协作关系
- 与 LPDT: 报告需求风险，申请 Charter 变更审批
- 与 SE: 澄清技术可行性对需求的影响
- 与 Developer: 解答需求疑问，验收实现结果
- 与 PQA: 确认需求验收标准被正确理解
禁止事项
- 不要提出无法实现的需求（需与 SE 对齐）
- 不要频繁变更 Charter（需走变更流程）
- 不要介入技术实现细节（留给 SE/Developer）
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 · 132 lines · 66 tokens per session scan A ed1eec8ab1f3
pdu is an agent published in the GitHub repository hatewx/oh-my-ipd (6 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 1,131 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 agents, from other repositories
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
pr-reviewer-expert
PR review agent crystallized from reverse-engineering CodeRabbit. Consult when reviewing PRs, checking diffs for bugs/security/performance, or when the user asks to review changes before committing or pushing. Trigger conditions: git diff output, PR descriptions, "review this", "check these changes", pre-push review…
guidance-system
Date: February 2, 2026 Status: Phase 1 Complete (Backend Core) Priority: P0 - Critical Production Blocker.