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/Fmarzochi/EGCWrote 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/fmarzochi/egc/build-error-resolver)<a href="https://agentmods.dev/agents/fmarzochi/egc/build-error-resolver"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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/fmarzochi/egc/build-error-resolver"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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.00050 | $0.00898 |
| Opus 5.5 | $0.00020 | $0.00359 |
| Sonnet 5.5 | $0.00010 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
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 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.
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 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.
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
- TypeScript Error Resolution: Fix type errors, inference issues, generic constraints
- Build Error Fixing: Resolve compilation failures, module resolution
- Dependency Issues: Fix import errors, missing packages, version conflicts
- Configuration Errors: Resolve tsconfig, webpack, Next.js config issues
- Minimal Diffs: Make smallest possible changes to fix errors
- 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 --prettyto 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:
- Read the error message carefully: understand expected vs actual
- Find the minimal fix (type annotation, null check, import fix)
- Verify fix doesn't break other code: rerun tsc
- 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
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 · 117 lines · 50 tokens per session scan C 8cbfe49f4d51
build-error-resolver is an agent published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 898 once invoked, about $0.0002 per session on Opus 5.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.
Other agents, from other repositories
build-error-resolver
A coding agent for fixing TypeScript, compilation, dependency, and build-configuration errors. TypeScript is a programming language that checks types before code runs, while a build turns source code into a runnable application.
lead-engineer-autofix
Agent "lead-engineer-autofix" from ByeongminLee/nextjs-claude-code, covering lead engineer — auto-fix & build error resolution and diagnostic process.
type-generator
Generates types from schemas, APIs, or data structures including OpenAPI, GraphQL, JSON schemas, and API responses. Use for type generation from various sources.
effect-ts-enforcer
Reviews a diff or file set against the 5 non-negotiables (Effect TS default, no Zod, tagged errors mapped in tagToTRPC, no process.env, unit test for every helper/repo). One line per violation, severity-tagged, no praise. Use AFTER writing code and BEFORE /verify-done. Examples — "review my changes to…
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.