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/qGolem/orcWrote 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/qgolem/orc/build-error-resolver)<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.
<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>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.01467 |
| Opus 5.5 | $0.00028 | $0.00587 |
| Sonnet 5.5 | $0.00014 | $0.00293 |
| Haiku 4.5 | $0.00007 | $0.00147 |
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` | 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
- Compilation Error Resolution — Fix type errors, borrow issues, ABI mismatches
- Build Error Fixing — Resolve compilation failures, module resolution
- Dependency Issues — Fix import errors, missing packages, version conflicts
- Configuration Errors — Resolve build tool config issues (tsconfig, Cargo.toml, foundry.toml)
- Minimal Diffs — Make smallest possible changes to fix errors
- 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:
- Read the error message carefully — understand expected vs actual
- Find the minimal fix (type annotation, null check, import fix, borrow fix)
- Verify fix doesn't break other code — rerun the check command
- Iterate until build passes
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 · 144 lines · 71 tokens per session scan C 2fd465d63036
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.
Other agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
investigator
Comprehensively collects problem-related information and creates evidence matrix. Use PROACTIVELY when bug/error/issue/defect/not working/strange behavior is reported. Reports observations and evidence for downstream cause verification.
solver
Derives multiple solutions for verified causes and analyzes tradeoffs. Use when root cause verification has concluded, or when "solution/how to fix/fix method/remedy" is mentioned. Focuses on solutions from given conclusions without investigation.
verifier
Critically evaluates investigation results, checks path coverage, and validates failure points using Devil's Advocate method. Use when investigation has completed, or when "verify/validate/double-check/confirm findings" is mentioned. Focuses on verification and conclusion derivation.
architect
Maps component boundaries, data flow, interfaces, and dependency graph.
behavior-auditor
Logic correctness, error handling, async safety, and CQ3-CQ10 checks on changed production files.