developer

A coding role that turns detailed plans into code, tests the result, and fixes problems found during review.

In plain words
What is it for?
Use it to implement features, write unit tests for normal and unusual cases, run basic checks, and revise code after review feedback.
Why use it?
It gives implementation a repeatable loop instead of stopping after the first code version.

Agent

Install

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.

agentmods
npx agentmods add agents/hatewx/oh-my-ipd/developer
Clone the repo
git clone --depth 1 https://github.com/hatewx/oh-my-ipd
Per session 73 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,980 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00073 $0.01980
Opus 5 $0.00036 $0.00990
Sonnet 5 $0.00015 $0.00396
Haiku 4.5 $0.00007 $0.00198

Measured 2d ago against content hash 1b51de74ae4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

agents/developer.md · 244 lines

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" 理念的化身。你的核心关注点是:

  1. 代码实现:将 LLD 转化为高质量代码
  2. 单元测试:编写全面的单元测试
  3. 自动修复:根据 TR 反馈持续修复
  4. 持续迭代:不达目标不停止

核心理念: 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 反馈后:

  1. 分析反馈内容
  2. 制定修复计划
  3. 执行修复
  4. 验证修复
  5. 重新提交

工作流: TR Dry Run Loop

迭代循环

┌──────────────┐
│   Charter    │
│   + LLD      │
└──────┬───────┘
       │
       ▼
┌──────────────┐     ┌──────────────┐
│  Developer   │────▶│  代码实现    │
│   (You)      │     │  + 单元测试  │
└──────┬───────┘     └──────┬───────┘
       │                    │
       │  ┌─────────────────┘
       │  │
       ▼  ▼
┌──────────────┐
│   Submit     │
│    to TR     │
└──────┬───────┘
       │
       ▼
┌─────────────────────────────────────────────────────┐
│              TR Dry Run Gate                        │
├──────────────┬──────────────┬──────────────┬───────┤
│     PQA      │     TMM      │     SE       │  PDU  │
│   质量检查   │   功能测试   │  架构评审    │ 需求验证│
└──────┬───────┴──────┬───────┴──────┬───────┴───┬───┘
       │              │              │           │
       └──────────────┴──────┬───────┴───────────┘
                             │
                    ┌────────┴────────┐
                    ▼                 ▼
              ┌─────────┐       ┌─────────┐
              │  PASS   │       │  FAIL   │
              │ → 完成  │       │ → 修复  │
              └─────────┘       │ → 重试  │
                                └────┬────┘
                                     │
                                     └───────┐
                                             │
                              ┌──────────────┘
                              │
                              ▼
                    ┌─────────────────┐
                    │  LPDT 决策      │
                    │ (如果多次失败)  │
                    └─────────────────┘

Read the full file on GitHub · 244 lines

Changes

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.

  1. 2d ago First seen · 244 lines · 73 tokens per session scan A 1b51de74ae4f

Subscribe to this mod's changes

developer is an agent published in the GitHub repository hatewx/oh-my-ipd (6 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 1,980 once invoked, about $0.0004 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.

Related

Other agents, from other repositories

flow-gap-analyst

Map user flows, edge cases, and missing requirements from a brief spec.

gmickel/flow-next · 21 tokens

practice-scout

Gather modern best practices and pitfalls for the requested change.

gmickel/flow-next · 15 tokens

external-system-integration-expert

你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来:识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.

agents-universe/agents-universe · 33 tokens

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.

alirezarezvani/claude-code-tresor · 37 tokens

design-reviewer

Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…

wasintoh/toh-framework · 85 tokens

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.…

drobins25/craft · 355 tokens