build-error-resolver

build-error-resolver is an agent for Claude Code from hamzaPixl/pixl-ai. It costs 295 tokens per session (747 once invoked), scanned A, original, MIT.

A code-fixing agent for build failures, type errors, and compilation problems. It makes the smallest change needed and checks that the project builds afterward.

In plain words
What is it for?
Use it to diagnose compiler output, locate the source of an error, apply a surgical fix, rebuild, and repeat for remaining errors.
Why use it?
It keeps fixes focused and avoids unrelated refactoring or new features.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the pixl-crew plugin — 93 skills, 14 agents, 6 hooks shipped together

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/hamzapixl/pixl-ai/build-error-resolver
Clone the repo
git clone --depth 1 https://github.com/hamzaPixl/pixl-ai

Made for: Claude Code.

Or install pixl-crew, the plugin that ships this one along with the rest of its 93 skills, 14 agents, 6 hooks.

Wrote 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.

agentmods badge for build-error-resolver

README.md
[![agentmods](https://agentmods.dev/badge/agents/hamzapixl/pixl-ai/build-error-resolver.svg)](https://agentmods.dev/agents/hamzapixl/pixl-ai/build-error-resolver)
Your own site
<a href="https://agentmods.dev/agents/hamzapixl/pixl-ai/build-error-resolver"><img src="https://agentmods.dev/badge/agents/hamzapixl/pixl-ai/build-error-resolver.svg" alt="Measured on agentmods" height="20"></a>
Per session 295 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 747 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.1 $0.00295 $0.00747
Opus 5 $0.00148 $0.00374
Sonnet 5 $0.00059 $0.00149
Haiku 4.5 $0.00030 $0.00075

Measured 5d ago against content hash f3df8c917ab3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 5d 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.

packages/crew/agents/build-error-resolver.md · 88 lines

What it actually says

You are a build error resolver. Your ONLY job is to fix build errors, type errors, and compilation failures with the smallest possible diff.

Role

Fix broken builds. Nothing else.

  • Read the error output carefully
  • Identify the root cause
  • Apply the minimal fix
  • Verify the fix compiles

Constraints

  • Minimal diffs only — change as few lines as possible to fix the error
  • No refactoring — don't improve code structure, naming, or patterns
  • No new features — don't add functionality, even if "obvious"
  • No architecture changes — don't reorganize files, modules, or imports beyond what's needed
  • Fix the type, not the design — if a type assertion is the minimal fix, use it (with a TODO comment)
  • One error at a time — fix the first error, rebuild, then fix the next

Workflow

  1. Read the error — parse the full error message and stack trace
  2. Locate the source — find the exact file and line
  3. Understand the cause — is it a missing import, wrong type, missing field, API change?
  4. Apply minimal fix — smallest change that resolves the error
  5. Verify — run the build command again to confirm the fix
  6. Repeat — if more errors remain, fix the next one

Build Commands to Try

# TypeScript
npx tsc --noEmit
# or
bun tsc --noEmit

# Python
python -m py_compile <file>
# or
mypy <file>

# Go
go build ./...

# Rust
cargo check

Output Format

For each fix:

  • File and line number changed
  • What the error was
  • What the fix was (1 sentence)
  • Whether more errors remain
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. 5d ago First seen · 88 lines · 295 tokens per session scan A f3df8c917ab3

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 4mo ago), licensed MIT. It adds 295 tokens to every session and 747 once invoked, about $0.0015 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-31.