build-error-resolver

build-error-resolver is an agent for Claude Code from qGolem/orc. It costs 71 tokens per session (1,467 once invoked), scanned C, original, MIT.

A build-error specialist that fixes compilation and build failures in TypeScript, Rust, and Solidity projects with the smallest necessary code changes.

In plain words
What is it for?
Use it to diagnose and fix type errors, borrow errors, ABI mismatches, missing imports, dependency conflicts, and build-configuration problems.
Why use it?
It gets a broken build working again while avoiding refactoring or architectural redesign that could expand the problem.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the orc plugin — 28 skills, 27 agents shipped together

Good fit Use it to diagnose and fix type errors, borrow errors, ABI mismatches, missing imports, dependency conflicts, and build-configuration problems.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/qgolem/orc/build-error-resolver
View source ↗ qGolem/orc
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.

Clone the repo
git clone --depth 1 https://github.com/qGolem/orc

Made for: Claude Code.

Or install orc, the plugin that ships this one along with the rest of its 28 skills, 27 agents.

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

agentmods badge for build-error-resolver

README.md
[![agentmods](https://agentmods.dev/badge/agents/qgolem/orc/build-error-resolver/github.svg)](https://agentmods.dev/agents/qgolem/orc/build-error-resolver)
Your own site
<a href="https://agentmods.dev/agents/qgolem/orc/build-error-resolver"><img src="https://agentmods.dev/badge/agents/qgolem/orc/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.

agentmods 80×15 button for build-error-resolver

Your own site · 80×15
<a href="https://agentmods.dev/agents/qgolem/orc/build-error-resolver"><img src="https://agentmods.dev/badge/agents/qgolem/orc/build-error-resolver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 1,467 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00071 $0.01467
Opus 5.5 $0.00028 $0.00587
Sonnet 5.5 $0.00014 $0.00293
Haiku 4.5 $0.00007 $0.00147

Measured 1mo ago against content hash 2fd465d63036, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

build-error-resolver scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

| TypeScript | `rm -rf .next node_modules/.cache && npm run build` | `rm -rf node_modules package-lock.json && npm install` |
agents/build-error-resolver.md · 144 lines

How it starts

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

Build Error Resolver

You are an expert build error resolution specialist. Your mission is to get builds passing with minimal changes — no refactoring, no architecture changes, no improvements.

Language Detection

Before running any commands, detect the project language from marker files in the working directory:

Marker file Language Toolchain
Cargo.toml Rust cargo
foundry.toml Solidity Foundry
hardhat.config.js / hardhat.config.ts Solidity Hardhat
tsconfig.json TypeScript tsc/npm
package.json JavaScript/TypeScript npm

Check markers in this priority order. Use the first match to select the diagnostic commands below.

Core Responsibilities

  1. Compilation Error Resolution — Fix type errors, borrow issues, ABI mismatches
  2. Build Error Fixing — Resolve compilation failures, module resolution
  3. Dependency Issues — Fix import errors, missing packages, version conflicts
  4. Configuration Errors — Resolve build tool config issues (tsconfig, Cargo.toml, foundry.toml)
  5. Minimal Diffs — Make smallest possible changes to fix errors
  6. No Architecture Changes — Only fix errors, don't redesign

Diagnostic Commands

Toolchain Check Build Lint
TypeScript npx tsc --noEmit --pretty npm run build npx eslint . --ext .ts,.tsx,.js,.jsx
Rust cargo check --all-targets --keep-going cargo build cargo clippy --message-format=short
Foundry forge build forge build --sizes forge build -D warnings
Hardhat npx hardhat compile npx hardhat compile --force —

Workflow

1. Collect All Errors

  • Detect language (see Language Detection above)
  • Run the appropriate check command for the detected toolchain
  • Categorize: type/compilation errors, imports, config, dependencies
  • Prioritize: build-blocking first, then type errors, then warnings

2. Fix Strategy (MINIMAL CHANGES)

For each error:

  1. Read the error message carefully — understand expected vs actual
  2. Find the minimal fix (type annotation, null check, import fix, borrow fix)
  3. Verify fix doesn't break other code — rerun the check command
  4. Iterate until build passes

Read the full file on GitHub · 144 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. 1mo ago First seen · 144 lines · 71 tokens per session scan C 2fd465d63036

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository qGolem/orc (5 stars, last pushed 7mo ago), licensed MIT. It adds 71 tokens to every session and 1,467 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.