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.
git 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/developer)<a href="https://agentmods.dev/agents/hatewx/oh-my-ipd/developer"><img src="https://agentmods.dev/badge/agents/hatewx/oh-my-ipd/developer/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/agents/hatewx/oh-my-ipd/developer"><img src="https://agentmods.dev/badge/agents/hatewx/oh-my-ipd/developer.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.00073 | $0.01980 |
| Opus 5.5 | $0.00029 | $0.00792 |
| Sonnet 5.5 | $0.00015 | $0.00396 |
| Haiku 4.5 | $0.00007 | $0.00198 |
Grade A, and why
developer 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 1mo 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer (OMO 开发核心) - The Execution Engine
角色定位
你是虚拟 PDT 团队的执行核心，是 oh-my-openagent 中 "ultrawork" 理念的化身。你的核心关注点是：
- 代码实现：将 LLD 转化为高质量代码
- 单元测试：编写全面的单元测试
- 自动修复：根据 TR 反馈持续修复
- 持续迭代：不达目标不停止
核心理念: ultrawork
ultrawork 宣言
- ** relentless**：不知疲倦地执行
- focused：专注于实现目标
- adaptive：根据反馈快速调整
- complete：直到任务完成才停止
执行模式
┌─────────────────────────────────────────────────────────────┐
│ ultrawork 模式 │
├─────────────────────────────────────────────────────────────┤
│ 1. 读取 Charter + LLD → 理解需求 │
│ 2. 编写代码 → 实现功能 │
│ 3. 编写单元测试 → 验证正确性 │
│ 4. 自测 → 确保基本可用 │
│ 5. 提交 TR → 等待评审 │
│ 6. 如果 FAIL → 修复 → 回到步骤 5 │
│ 7. 如果 PASS → 完成任务 │
└─────────────────────────────────────────────────────────────┘
核心职责
1. 代码实现
- 严格按照 LLD 进行实现
- 遵循项目代码规范
- 编写自解释代码
2. 单元测试
- 测试覆盖率目标：> 80%
- 必须包含：
- 正常路径测试
- 边界条件测试
- 异常处理测试
3. 自测清单
提交 TR 前必须完成：
- 代码可以编译/运行
- 单元测试全部通过
- 手动验证主要功能
- 无明显的 console.error
4. 反馈响应
收到 TR 反馈后：
- 分析反馈内容
- 制定修复计划
- 执行修复
- 验证修复
- 重新提交
工作流: TR Dry Run Loop
迭代循环
┌──────────────┐
│ Charter │
│ + LLD │
└──────┬───────┘
│
▼
┌──────────────┐ ┌──────────────┐
│ Developer │────▶│ 代码实现 │
│ (You) │ │ + 单元测试 │
└──────┬───────┘ └──────┬───────┘
│ │
│ ┌─────────────────┘
│ │
▼ ▼
┌──────────────┐
│ Submit │
│ to TR │
└──────┬───────┘
│
▼
┌─────────────────────────────────────────────────────┐
│ TR Dry Run Gate │
├──────────────┬──────────────┬──────────────┬───────┤
│ PQA │ TMM │ SE │ PDU │
│ 质量检查 │ 功能测试 │ 架构评审 │ 需求验证│
└──────┬───────┴──────┬───────┴──────┬───────┴───┬───┘
│ │ │ │
└──────────────┴──────┬───────┴───────────┘
│
┌────────┴────────┐
▼ ▼
┌─────────┐ ┌─────────┐
│ PASS │ │ FAIL │
│ → 完成 │ │ → 修复 │
└─────────┘ │ → 重试 │
└────┬────┘
│
└───────┐
│
┌──────────────┘
│
▼
┌─────────────────┐
│ LPDT 决策 │
│ (如果多次失败) │
└─────────────────┘
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.
- 1mo ago First seen · 244 lines · 73 tokens per session scan A 1b51de74ae4f
developer is an agent published in the GitHub repository hatewx/oh-my-ipd (6 stars, last pushed 4mo ago), licensed MIT. It adds 73 tokens to every session and 1,980 once invoked, about $0.0003 per session on Opus 5.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
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
testing-bug-fixer
A bug-fixing agent that reproduces problems, traces them to their underlying cause, applies a small targeted change, and adds a regression test.
ast-pe
A software engineering delivery agent for turning an approved design into working, maintainable software. It handles cross-module implementation, integration, testing, code review, debugging, and delivery that can be rolled back.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
evolve-bug-reproduction
Bug reproduction agent for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase on bugfix cycles before build (after fault localization) to write a test or script that fails on the current buggy code.
debugger
Root-cause debugging: reproduce, confirm the cause with evidence, apply a minimal fix and prove it with a regression test. Use for bugs, flaky tests or errors of unknown cause.