build-error-resolver

build-error-resolver is an agent for coding agents from Fmarzochi/EGC. It costs 50 tokens per session (898 once invoked), scanned C, a copy of build-error-resolver, Apache-2.0.

A build and TypeScript error-fixing assistant that focuses on the smallest changes needed to make a project compile successfully.

In plain words
What is it for?
Use it to diagnose and fix TypeScript errors, compilation failures, module-resolution issues, dependency conflicts, and configuration errors.
Why use it?
It helps when a build is blocked by type errors, missing imports, dependency problems, or configuration mistakes without turning the fix into a broader redesign.

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/fmarzochi/egc/build-error-resolver
Clone the repo
git clone --depth 1 https://github.com/Fmarzochi/EGC

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/fmarzochi/egc/build-error-resolver.svg)](https://agentmods.dev/agents/fmarzochi/egc/build-error-resolver)
Your own site
<a href="https://agentmods.dev/agents/fmarzochi/egc/build-error-resolver"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/build-error-resolver.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 898 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00050 $0.00898
Opus 5 $0.00025 $0.00449
Sonnet 5 $0.00010 $0.00180
Haiku 4.5 $0.00005 $0.00090

Measured 3d ago against content hash 8cbfe49f4d51, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

rm -rf .next node_modules/.cache && npm run build
Origin

This is a copy

100% identical to build-error-resolver — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.kiro/agents/build-error-resolver.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 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.

Core Responsibilities

  1. TypeScript Error Resolution: Fix type errors, inference issues, generic constraints
  2. Build Error Fixing: Resolve compilation failures, module resolution
  3. Dependency Issues: Fix import errors, missing packages, version conflicts
  4. Configuration Errors: Resolve tsconfig, webpack, Next.js config issues
  5. Minimal Diffs: Make smallest possible changes to fix errors
  6. No Architecture Changes: Only fix errors, don't redesign

Diagnostic Commands

npx tsc --noEmit --pretty
npx tsc --noEmit --pretty --incremental false   # Show all errors
npm run build
npx eslint . --ext .ts,.tsx,.js,.jsx

Workflow

1. Collect All Errors

  • Run npx tsc --noEmit --pretty to get all type errors
  • Categorize: type inference, missing types, imports, config, dependencies
  • Prioritize: build-blocking first, then type errors, then warnings

2. Fix Strategy (MINIMAL CHANGES)

For each error:

  1. Read the error message carefully: understand expected vs actual
  2. Find the minimal fix (type annotation, null check, import fix)
  3. Verify fix doesn't break other code: rerun tsc
  4. Iterate until build passes

3. Common Fixes

Error Fix
implicitly has 'any' type Add type annotation
Object is possibly 'undefined' Optional chaining ?. or null check
Property does not exist Add to interface or use optional ?
Cannot find module Check tsconfig paths, install package, or fix import path
Type 'X' not assignable to 'Y' Parse/convert type or fix the type
Generic constraint Add extends { ... }
Hook called conditionally Move hooks to top level
'await' outside async Add async keyword

DO and DON'T

DO:

  • Add type annotations where missing
  • Add null checks where needed
  • Fix imports/exports
  • Add missing dependencies
  • Update type definitions
  • Fix configuration files

Read the full file on GitHub · 117 lines

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. 3d ago First seen · 117 lines · 50 tokens per session scan C 8cbfe49f4d51

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository Fmarzochi/EGC (46 stars, last pushed 7d ago), licensed Apache-2.0. It adds 50 tokens to every session and 898 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 100% identical to build-error-resolver, differing in 18 lines, and is treated as a copy.

Related

Other agents, from other repositories

test-hunter

Generates adversarial tests for a module or feature. Does NOT write happy-path tests — that is the author's job. Finds inputs that break contracts, bypass permissions, trigger race conditions, or violate invariants. Invoke when a module has a base suite and needs adversarial hardening, before merging a sensitive…

jghiringhelli/forgecraft-mcp · 83 tokens

change-reviewer

Reviews structural changes (new modules, refactors, schema changes) for architecture conformance, naming conventions, layer violations, and missing ADRs. Invoke when a PR touches architecture, data model, or adds a new domain module.

jghiringhelli/forgecraft-mcp · 50 tokens

security-reviewer

Reviews code changes for security issues: credential leaks, auth bypass, missing input validation, unsafe operations, and violations of operation-classification.md. Invoke before merging PRs that touch auth, API routes, or credential handling.

jghiringhelli/forgecraft-mcp · 48 tokens

spec-guardian

Verifies the codebase is in sync with the spec (PRD.md, use-cases.md, ADRs, data-model.md). Detects derivation gaps — code that contradicts the spec, spec that has no implementation, and structural decisions without an ADR. Invoke before cutting a release or when drift is suspected.

jghiringhelli/forgecraft-mcp · 69 tokens

test-engineer

QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.

addyosmani/agent-skills · 35 tokens

shep-web-route-creator

Scaffolds ONE new Next.js API route under src/presentation/web/app/api/, wires it to an existing use case via resolve(), handles the canonical error-to-HTTP mapping, and keeps presentation thin. Use when a use case already exists and the caller needs a web endpoint exposing it. Does NOT create the use case, does NOT…

shep-ai/shep · 85 tokens