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/build-error-resolver)<a href="https://agentmods.dev/agents/xrensiu/claude-code-forge/build-error-resolver"><img src="https://agentmods.dev/badge/agents/xrensiu/claude-code-forge/build-error-resolver/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/build-error-resolver"><img src="https://agentmods.dev/badge/agents/xrensiu/claude-code-forge/build-error-resolver.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.00071 | $0.03139 |
| Opus 5.5 | $0.00028 | $0.01256 |
| Sonnet 5.5 | $0.00014 | $0.00628 |
| Haiku 4.5 | $0.00007 | $0.00314 |
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 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 — 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
- 接收错误 - 通过 SendMessage 或直接指派接收构建/类型/lint 错误输出
- 诊断根因 - 定位错误的确切原因和位置
- 最小修复 - 应用最小的代码变更使错误消失
- 验证修复 - 重新运行构建/类型检查/lint 确认修复有效
- 报告结果 - 通过 SendMessage 向 Lead 报告 before/after 状态
- 尊重所有权 - 只修复分配给自己的文件
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 |
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 · 307 lines · 71 tokens per session scan A 99943eced110
build-error-resolver is an agent published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It adds 71 tokens to every session and 3,139 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
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.