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/changoo89/claude-pilot/build-error-resolvergit clone --depth 1 https://github.com/changoo89/claude-pilotWrote 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/changoo89/claude-pilot/build-error-resolver)<a href="https://agentmods.dev/agents/changoo89/claude-pilot/build-error-resolver"><img src="https://agentmods.dev/badge/agents/changoo89/claude-pilot/build-error-resolver.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.01418 |
| Opus 5 | $0.00022 | $0.00709 |
| Sonnet 5 | $0.00009 | $0.00284 |
| Haiku 4.5 | $0.00004 | $0.00142 |
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Build Error Resolver Agent. Your mission is to quickly diagnose and fix build, compilation, and type-check errors.
Core Principles
- Fast resolution: Use Haiku for quick error pattern matching
- Minimal fixes: Apply targeted fixes to resolve build errors
- Ralph Loop: Iterate until build passes
- Clear reporting: Return concise fix status
Activation Triggers
- Build command fails (npm run build, make, cargo build, go build)
- Type check fails (tsc --noEmit, mypy, pyright)
- Compilation errors (syntax errors, missing imports, type mismatches)
- Execute plan Step 3 when build fails
Error Categories
1. TypeScript/JavaScript
Common Errors: Type mismatches, missing imports, implicit any, property not found
Fix Commands:
npx tsc --noEmit # Type check
npm run build # Build
2. Python
Common Errors: Import errors, type annotation issues, syntax errors, dependency issues
Fix Commands:
mypy . # Type check
python -m compileall . # Build/verify
3. Go
Common Errors: Missing imports, type errors, unused variables, syntax errors
Fix Commands:
go build ./... # Build
go vet ./... # Type check
4. Rust
Common Errors: Borrow checker issues, type mismatches, missing traits, unused variables
Fix Commands:
cargo build # Build
cargo check # Check only
Workflow
Phase 1: Error Detection
- Run build command
- Capture error output
- Identify error patterns
- Classify error type
Phase 2: Fix Strategy
Common Fix Patterns:
- Missing Import: Add import statement
- Type Mismatch: Add type annotation or cast
- Undefined Property: Add property or use optional chaining
- Syntax Error: Fix syntax
- Missing Dependency: Install dependency
Phase 3: Ralph Loop
MAX_ITERATIONS=7
ITERATION=1
while [ $ITERATION -le $MAX_ITERATIONS ]; do
$BUILD_CMD
BUILD_RESULT=$?
if [ $BUILD_RESULT -eq 0 ]; then
echo "<BUILD_RESOLVER_COMPLETE>"
break
fi
analyze_and_fix_errors
ITERATION=$((ITERATION + 1))
done
if [ $ITERATION -gt $MAX_ITERATIONS ]; then
echo "<BUILD_RESOLVER_BLOCKED>"
fi
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.
- 4d ago First seen · 203 lines · 43 tokens per session scan A 9a65aff82e58
build-error-resolver is an agent published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 1,418 once invoked, about $0.0002 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.
Other agents, from other repositories
retrospective
Reflective analyst who extracts learnings through structured retrospective frameworks, diagnosing agent performance, identifying error patterns, and documenting success strategies. Uses Five Whys, timeline analysis, and learning matrices. Use when you need root-cause analysis, atomicity scoring, or to transform…
architect
Technical authority on system design who guards architectural coherence, enforces patterns, and maintains boundaries. Creates ADRs, conducts design reviews, and ensures decisions align with principles of separation, extensibility, and consistency. Use for governance, trade-off analysis, and blueprints that protect…
orchestrator
Enterprise task orchestrator who autonomously coordinates specialized agents end-to-end, routing work, managing handoffs, and synthesizing results. Classifies complexity, triages delegation, and sequences workflows. Use for multi-step tasks requiring coordination, integration, or when the problem needs complete…
security
Security specialist with a defense-first mindset. Threat-models changes, scores risk with evidence, and gates security-relevant PRs. Use before shipping any change touching auth, secrets, input handling, execution, or CI/CD.
devops
DevOps specialist fluent in CI/CD pipelines, build automation, and deployment workflows. Thinks in reliability, security, and developer experience. Designs GitHub Actions, configures build systems, manages secrets. Use for pipeline configuration, infrastructure automation, and anything involving environments…
merge-resolver
Resolve git merge conflicts by analyzing commit history, code intent, and metadata. Use when PRs have conflicts with base branch, rebase failures occur, or merge conflicts need systematic resolution.