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/affaan-m/ecc/build-error-resolvergit clone --depth 1 https://github.com/affaan-m/ECCWhat 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.00050 | $0.00898 |
| Opus 5 | $0.00025 | $0.00449 |
| Sonnet 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 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 Copies of this mod
8 near-identical copies found in the catalogue:
- build-error-resolver — 100% identical, 0 lines differ
- build-error-resolver — 100% identical, 0 lines differ
- build-error-resolver — 100% identical, 0 lines differ
- build-error-resolver — 100% identical, 18 lines differ
- build-error-resolver — 100% identical, 0 lines differ
- build-error-resolver — 100% identical, 0 lines differ
- build-error-resolver — 98% identical, 6 lines differ
- build-error-resolver — 98% identical, 6 lines differ
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.
- 3d ago First seen · 117 lines · 50 tokens per session scan C efdd73b2413e
build-error-resolver is an agent published in the GitHub repository affaan-m/ECC (245,751 stars, last pushed 2d ago), licensed MIT. 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). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
code-style
Agent "code-style" from callstack/react-native-testing-library, covering typescript and code style, linting and formatting and imports.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
ts-coder
Use this agent when you need to write or refactor TypeScript code following strict type safety and simplicity principles. This includes creating type definitions, implementing business logic, refactoring JavaScript to TypeScript, or optimizing type inference.
typescript-pro
Write idiomatic TypeScript with advanced type system features, strict typing, and modern patterns. Masters generic constraints, conditional types, and type inference. Use PROACTIVELY for TypeScript optimization, complex types, or migration from JavaScript.
node-developer
Senior Node.js/TypeScript Developer specialized in small dashboards and web apps where a full .NET stack would be overkill. Expert in TypeScript, Next.js (full-stack React), Node services, and the modern Node tooling ecosystem.
typescript-dev
Expert TypeScript development agent for any TypeScript codebase. Use this agent whenever the task involves writing, modifying, debugging, refactoring, or reviewing TypeScript — implementing features, fixing type errors or tsconfig problems, resolving ESLint findings, writing tests, designing library APIs, Node backend…