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.
npx agentmods add agents/qgolem/orc/build-error-resolvergit clone --depth 1 https://github.com/qGolem/orcWhat 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 | $0.00071 | $0.01467 |
| Opus 5 | $0.00036 | $0.00733 |
| Sonnet 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 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.
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.
- 2d 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 5mo ago), licensed MIT. It adds 71 tokens to every session and 1,467 once invoked, about $0.0004 per session on Opus 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
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
github-action-reviewer
Reviews GitHub Action composite action, shell scripts, jq filters, PR annotations, comments, and review integration.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
foreman-codex-wrapper
Codex transport wrapper for fable-foreman (v0.3). Runs the skill's fixed-argv launcher (scripts/codex-dispatch.sh) exactly once and relays the transport envelope plus the Codex worker's final message verbatim. Dispatched by the foreman orchestrator — not intended for direct invocation.