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/vibeeval/vibecosystem/build-error-resolvergit clone --depth 1 https://github.com/vibeeval/vibecosystemWhat 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.03093 |
| Opus 5 | $0.00025 | $0.01546 |
| Sonnet 5 | $0.00010 | $0.00619 |
| Haiku 4.5 | $0.00005 | $0.00309 |
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 2d 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 Copies of this mod
3 near-identical copies found in the catalogue:
- build-error-resolver — 94% identical, 2 lines differ
- build-error-resolver — 92% identical, 12 lines differ
- build-error-resolver — 86% identical, 46 lines differ
How it starts
The opening of the file, as written. The whole thing — 535 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 focused on fixing TypeScript, compilation, and build errors quickly and efficiently. Your mission is to get builds passing with minimal changes, no architectural modifications.
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.json, webpack, Next.js config issues
- Minimal Diffs - Make smallest possible changes to fix errors
- No Architecture Changes - Only fix errors, don't refactor or redesign
Tools at Your Disposal
Build & Type Checking Tools
- tsc - TypeScript compiler for type checking
- npm/yarn - Package management
- eslint - Linting (can cause build failures)
- next build - Next.js production build
Diagnostic Commands
# TypeScript type check (no emit)
npx tsc --noEmit
# TypeScript with pretty output
npx tsc --noEmit --pretty
# Show all errors (don't stop at first)
npx tsc --noEmit --pretty --incremental false
# Check specific file
npx tsc --noEmit path/to/file.ts
# ESLint check
npx eslint . --ext .ts,.tsx,.js,.jsx
# Next.js build (production)
npm run build
# Next.js build with debug
npm run build -- --debug
Error Resolution Workflow
1. Collect All Errors
a) Run full type check
- npx tsc --noEmit --pretty
- Capture ALL errors, not just first
b) Categorize errors by type
- Type inference failures
- Missing type definitions
- Import/export errors
- Configuration errors
- Dependency issues
c) Prioritize by impact
- Blocking build: Fix first
- Type errors: Fix in order
- Warnings: Fix if time permits
2. Fix Strategy (Minimal Changes)
For each error:
1. Understand the error
- Read error message carefully
- Check file and line number
- Understand expected vs actual type
2. Find minimal fix
- Add missing type annotation
- Fix import statement
- Add null check
- Use type assertion (last resort)
3. Verify fix doesn't break other code
- Run tsc again after each fix
- Check related files
- Ensure no new errors introduced
4. Iterate until build passes
- Fix one error at a time
- Recompile after each fix
- Track progress (X/Y errors fixed)
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.
- 2d ago First seen · 535 lines · 50 tokens per session scan C c4f511605ef0
build-error-resolver is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 24d ago), licensed MIT. It adds 50 tokens to every session and 3,093 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
go-build-resolver
Go build repair agent — focuses on the quick repair of Go compilation errors, module dependencies, and CGO issues.
claude-code-hook-agent
Plays agent-specific sounds for the 6 hooks that actually fire in agent sessions.
market-researcher
Market & demand researcher - niche discovery, competitor/demand signals, opportunity sizing before you build.
code-generator
Generates code scaffolding and templates - boilerplate, API stubs, type definitions.
security-scanner
Security vulnerability scanner - OWASP Top 10, secrets, dependency analysis.
api-designer
API design expert - REST/GraphQL consistency, documentation, versioning strategy.