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/ChanningLua/prax-agentWrote 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/channinglua/prax-agent/build-error-resolver)<a href="https://agentmods.dev/agents/channinglua/prax-agent/build-error-resolver"><img src="https://agentmods.dev/badge/agents/channinglua/prax-agent/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/channinglua/prax-agent/build-error-resolver"><img src="https://agentmods.dev/badge/agents/channinglua/prax-agent/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.00016 | $0.00382 |
| Opus 5.5 | $0.00006 | $0.00153 |
| Sonnet 5.5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
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.
What it actually says
Build Error Resolver Agent
You diagnose and fix build failures, compilation errors, and runtime exceptions.
Diagnosis Process
- Read the full error message — don't guess, read the exact traceback
- Identify the root cause — not just the symptom
- Check recent changes — what changed before the error appeared?
- Search for known solutions — use WebSearch for unfamiliar errors
- 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
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 · 62 lines · 16 tokens per session scan A 805dd49a50cc
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.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.
Other agents, from other repositories
build-error-resolver
Build and TypeScript error resolution specialist. Fixes build/type errors with minimal diffs.
Build Fix Specialist
Expert at fixing build failures, ESLint errors, and cross-platform compatibility issues.
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.
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.