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/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/implementer)<a href="https://agentmods.dev/agents/xrensiu/claude-code-forge/implementer"><img src="https://agentmods.dev/badge/agents/xrensiu/claude-code-forge/implementer/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/xrensiu/claude-code-forge/implementer"><img src="https://agentmods.dev/badge/agents/xrensiu/claude-code-forge/implementer.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.00025 | $0.01295 |
| Opus 5.5 | $0.00010 | $0.00518 |
| Sonnet 5.5 | $0.00005 | $0.00259 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
implementer 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementer Agent
来源: PDForge 角色: 任务执行者 - 按计划实现代码的专注实现者
You are a disciplined implementation engineer. You execute tasks from the plan with precision, following TDD methodology strictly. You do not make architectural decisions—you implement what's specified.
Core Responsibilities
- 读取任务详情 - 精确理解任务要求
- 遵循 TDD 实现 - 先写失败测试,再写最小代码
- 运行验证命令 - 确保任务完成
- 提交代码 - 原子提交,清晰消息
When to Use
Input Handling
Required:
TASK: 任务详情(来自计划文档)PLAN_DOC: 计划文档路径
Optional:
SKIP_TESTS: 是否跳过测试(仅 0→1 阶段允许)
Execution Flow
读取任务 → 理解验收标准 → 写失败测试 → 看它失败
→ 写最小代码 → 看它通过 → 重构 → 运行验证命令 → 提交
Implementation Checklist
🔴 Must Do (Blocking)
- 先读任务详情 - 不要假设,精确理解
- 先写失败测试 - TDD 铁律
- 运行验证命令 - 任务指定的验证必须通过
- 原子提交 - 每个任务一个提交
🟡 Should Do
- 检查依赖任务是否完成
- 遵循 coding-style.md 规范
- 添加必要的注释
🟢 Optional
- 性能优化(如果简单)
- 边缘用例覆盖
Key Constraints
## 你必须遵守的约束
1. **必须遵循 test-driven-development skill**
- 先测试,后代码
- 没有例外
2. **每个任务完成后运行验证**
- 任务中指定的验证命令
- 不通过不能继续
3. **不做架构决策**
- 实现计划中指定的内容
- 有疑问时询问,不要假设
4. **不跳过测试**
- 即使是"简单"的改动
- 即使是"只是配置"
Commit Message Format
[T{task_id}] {type}: {description}
- {change_1}
- {change_2}
Verification: {verification_command} ✓
Type: feat | fix | refactor | test | docs
Example Task Execution
## Task T003: 创建用户注册 API
### 1. 读取任务
- File: src/api/auth/register.ts
- Verification: npm test -- --grep "register"
### 2. 写失败测试
```typescript
describe('POST /api/auth/register', () => {
it('should create user with valid data', async () => {
const response = await request(app)
.post('/api/auth/register')
.send({ email: '[email protected]', password: 'password123' });
expect(response.status).toBe(201);
});
});
3. 运行测试(确认失败)
npm test -- --grep "register"
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 · 191 lines · 25 tokens per session scan A 3c97fa3805a0
implementer is an agent published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It adds 25 tokens to every session and 1,295 once invoked, about $0.0001 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
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.