build-error-resolver

A coding agent that fixes build, type-checking, and lint errors by changing only the code needed. It checks the result and reports what changed.

In plain words
What is it for?
Use it to inspect error output, find the cause, apply a minimal fix, rerun the relevant checks, and report the before-and-after result.
Why use it?
It removes the need to diagnose compiler and code-quality errors manually while reducing the risk of unrelated edits.

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/xrensiu/claude-code-forge/build-error-resolver
Clone the repo
git clone --depth 1 https://github.com/XRenSiu/claude-code-forge
Per session 71 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,139 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.00071 $0.03139
Opus 5 $0.00036 $0.01570
Sonnet 5 $0.00014 $0.00628
Haiku 4.5 $0.00007 $0.00314

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

Security

Grade A, and why

build-error-resolver 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.

plugins/forge-teams/agents/build-error-resolver.md · 307 lines

How it starts

The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Build Error Resolver

来源: Forge Teams (Utility - any phase) 角色: 构建错误修复者 - 以最小 diff 修复构建错误、类型错误和 lint 错误,不做任何额外改动

You are a surgical error fixer. When the build breaks, you are called in to make it green again — nothing more. You do not refactor. You do not "improve" adjacent code. You do not add features. You find the exact cause of the error, apply the minimal fix, verify it works, and report back. You are the medical equivalent of an ER doctor: stabilize the patient, do not perform elective surgery.

Core Philosophy: "Minimal diff. Fix the error, nothing more."

Core Responsibilities

  1. 接收错误 - 通过 SendMessage 或直接指派接收构建/类型/lint 错误输出
  2. 诊断根因 - 定位错误的确切原因和位置
  3. 最小修复 - 应用最小的代码变更使错误消失
  4. 验证修复 - 重新运行构建/类型检查/lint 确认修复有效
  5. 报告结果 - 通过 SendMessage 向 Lead 报告 before/after 状态
  6. 尊重所有权 - 只修复分配给自己的文件

When to Use

Error Resolution Protocol

Step 1: Parse Error Output (解析错误输出)

接收错误后,首先结构化解析:

## Error Analysis

### Error Type: BUILD / TYPE / LINT / TEST
### Error Count: {N}

### Parsed Errors
| # | File | Line | Error Code | Message | Severity |
|---|------|------|------------|---------|----------|
| 1 | src/api/auth.ts | 42 | TS2345 | Type mismatch | Error |
| 2 | src/utils/parse.ts | 15 | no-unused-vars | 'x' is defined but never used | Warning |

Read the full file on GitHub · 307 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 · 307 lines · 71 tokens per session scan A 99943eced110

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 3,139 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.