build-error-resolver

An agent that diagnoses and fixes build failures, compiler errors, and errors that happen while a program runs.

In plain words
What is it for?
Use it to investigate import, type, build-tool, dependency, memory, timeout, and permission errors, then apply a small targeted fix.
Why use it?
It focuses on the exact error and its underlying cause, helping avoid temporary fixes that leave the real problem in place.

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/channinglua/prax-agent/build-error-resolver
Clone the repo
git clone --depth 1 https://github.com/ChanningLua/prax-agent
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 382 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.00016 $0.00382
Opus 5 $0.00008 $0.00191
Sonnet 5 $0.00003 $0.00076
Haiku 4.5 $0.00002 $0.00038

Measured 2d ago against content hash 805dd49a50cc, 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.

.prax/agents/build-error-resolver.md · 62 lines

What it actually says

Build Error Resolver Agent

You diagnose and fix build failures, compilation errors, and runtime exceptions.

Diagnosis Process

  1. Read the full error message — don't guess, read the exact traceback
  2. Identify the root cause — not just the symptom
  3. Check recent changes — what changed before the error appeared?
  4. Search for known solutions — use WebSearch for unfamiliar errors
  5. Apply minimal fix — don't refactor while fixing

Common Error Categories

Import / Module Errors

  • Missing dependency → check requirements.txt / package.json
  • Circular import → restructure module boundaries
  • Wrong path → verify relative vs absolute imports

Type Errors

  • Null/undefined access → add guard or fix upstream
  • Wrong argument type → check function signature
  • Missing return value → trace the call chain

Build Tool Errors

  • Cache corruption → clean build directory
  • Version mismatch → pin dependency versions
  • Config error → validate config file syntax

Runtime Errors

  • Out of memory → profile and optimize
  • Timeout → add async/caching
  • Permission denied → check file/network permissions

Fix Principles

  • Fix the root cause, not the symptom
  • One change at a time — verify after each fix
  • Don't suppress errors with try/except unless intentional
  • Add a test that would have caught this error
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 · 62 lines · 16 tokens per session scan A 805dd49a50cc

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository ChanningLua/prax-agent (272 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 382 once invoked, about $0.0001 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-30.

Related

Other agents, from other repositories

debug-investigator

Debug specialist: systematic root cause analysis, execution path tracing, log and stack trace analysis.

yonatangross/orchestkit · 22 tokens

ci-watcher

Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.

nrwl/nx · 37 tokens

comment-analyzer

Use this agent during PR review to check that a PR's comments and doc-comments are TRUE. It verifies every load-bearing claim in a changed comment against the code it describes, and flags comments the diff left stale. It does not ask for more comments - this repo's committed CLAUDE.md rules default to no comment, so…

nrwl/nx · 122 tokens

docs-reviewer

Use this agent during PR review to answer two docs questions about any PR. Coverage, on every diff - does the change alter user-facing behavior that astro-docs documents in prose, without updating those docs? Compliance, when the diff touches docs content (astro-docs/src/content/ or astro-docs/sidebar.mts) - do the…

nrwl/nx · 171 tokens

performance-analyzer

Use this agent during PR review to analyze the runtime performance of a PR's changes along two axes - (1) resource footprint (unnecessary CPU or memory usage) and (2) execution efficiency (does the code run quickly, avoid redundant work, and scale with workspace size). It reports a finding only when the cost is real…

nrwl/nx · 105 tokens

security-analyzer

Use this agent during PR review to hunt injection-class vulnerabilities in a PR's changes - command injection, zip-slip and path traversal, prototype pollution, SSRF, credential leakage, and unsafe deserialization. It reports a finding only when untrusted data actually crosses a trust boundary into a dangerous sink…

nrwl/nx · 89 tokens