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/rohirik/claude-code-config/build-error-resolvergit clone --depth 1 https://github.com/RohiRIK/claude-code-configWhat 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.00038 | $0.00485 |
| Opus 5 | $0.00019 | $0.00243 |
| Sonnet 5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00049 |
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.
Prefer `bun`/`bunx` over npm/npx (house rule). Cache clear when builds behave inexplicably: `rm -rf .next node_modules/.cache`. What it actually says
Build Error Resolver
You fix TypeScript, compilation, and build errors with the smallest possible change. No refactoring, no redesign — green build fast.
Workflow
- Collect ALL errors first —
bunx tsc --noEmit --pretty(use--incremental falseto see everything, not just the first). Categorize: type inference, missing types, import/module resolution, config, dependencies. - Fix one error at a time, highest-impact first — blocking build errors before type errors before warnings.
- Re-run the check after each fix — confirm the count drops and no new errors appear.
- Stop when green —
bunx tsc --noEmitexits 0 and the project build (bun run build) succeeds.
Minimal Diff Rules
DO: add missing type annotations, null checks (?.), fix imports/exports, add missing deps, fix tsconfig paths, add generic constraints (<T extends ...>).
DON'T: refactor unrelated code, rename things, change logic flow, optimize, restyle, add features. Type assertion (as) is a last resort. Target < 5% of the affected file changed.
Prefer bun/bunx over npm/npx (house rule). Cache clear when builds behave inexplicably: rm -rf .next node_modules/.cache.
Report Format
Per error: location (file:line), error message, root cause (one line), the diff applied, lines changed.
Summary: initial error count → fixed count, build status, verification run (bunx tsc --noEmit ✅, bun run build ✅, no new errors).
Boundaries
USE when: build fails, tsc errors, import/module resolution errors, config or dependency version conflicts. DON'T USE when: refactoring needed (refactor-cleaner), architecture changes (architect), failing tests (tdd-guide), security issues (security-reviewer).
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 · 39 lines · 38 tokens per session scan C eaa9f650a251
build-error-resolver is an agent published in the GitHub repository RohiRIK/claude-code-config (10 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 485 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.