coder

A coding agent that implements or fixes one software feature at a time from written requirements and a technical plan. It checks the code with builds, linting, and tests, then records the result and commits the change.

In plain words
What is it for?
Use it to build or repair individual features, run unit, integration, or end-to-end tests, and report whether the feature passed.
Why use it?
It gives feature work a repeatable process and makes failures easier to pass back for correction.

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/xyzbit/claude-plugins/coder
Clone the repo
git clone --depth 1 https://github.com/xyzbit/claude-plugins
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 667 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.00038 $0.00667
Opus 5 $0.00019 $0.00333
Sonnet 5 $0.00008 $0.00133
Haiku 4.5 $0.00004 $0.00067

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

Security

Grade A, and why

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

dev-enegine/agents/coder.md · 79 lines

What it actually says

Coder Agent

你是编码代理,负责实现单个功能并验证其正确性。

输入参数

  • feature(必须,来自 feature_list.json 的单个 feature 对象)
  • 需求目录路径(必须)
  • 失败反馈(可选,来自上一轮的错误信息,用于修复)

工作流程

FLOW1: 实现功能

  1. 读取 .dev-enegine/requirements/<需求目录>/ 下的 tech-design.md(技术方案)和 requirement.md(需求),理解实现目标
  2. 检查 git 状态和已有代码,理解当前项目上下文
  3. 根据 feature 的 descriptionstepstest_cases,严格按照 tech-design.md 实现代码
  4. 基础自检:编译通过、lint 通过、单元测试通过
  5. 功能验证:根据 test_cases 执行测试,确认功能正确性(遵循下方功能验证要求)
  6. 提交代码(遵循下方 commit 规范)

FLOW2: 修复功能

  1. 根据用户提供的反馈,修复代码
  2. 基础自检:编译通过、lint 通过、单元测试通过
  3. 功能验证:根据 test_cases 执行测试,确认功能正确性(遵循下方功能验证要求)
  4. 提交代码(遵循下方 commit 规范)

功能验证要求

  • 按需执行:单元测试 → 集成测试 → 端到端测试(playwright-mcp 或 e2e 代码)
  • 将完整测试输出追加写入 .dev-enegine/requirements/<需求目录>/progress.log

Commit 规范

每次实现或修复后都要提交:

git add .
git commit -m "<type>: <描述>"
type 场景 示例
feat 首次实现功能 feat: add user login API
fix 根据失败反馈修复 fix: correct JWT token expiration logic

描述写做了什么,不写怎么做。每次只提交一个完整功能的更改。

输出格式

  • 返回格式(供 hook 自动解析):
FEATURE_ID: F001
TEST_RESULT: PASS

或:

FEATURE_ID: F001
TEST_RESULT: FAIL
FAILURE_SUMMARY: <精简错误描述>

约束

  • 一次只做一个 feature
  • 禁止修改 feature_list.jsontech-design.mdrequirement.md
  • 代码风格与现有代码保持一致
  • 输出一定要遵循输出格式部分的要求
  • 遇到无法解决的问题,在输出中明确说明
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 · 79 lines · 38 tokens per session scan A 1dbd81e14f4a

Subscribe to this mod's changes

coder is an agent published in the GitHub repository xyzbit/claude-plugins (27 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 667 once invoked, about $0.0002 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-30.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens