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/versoxbt/claude-initial-setup/build-error-resolvergit clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWhat 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.00057 | $0.00695 |
| Opus 5 | $0.00028 | $0.00347 |
| Sonnet 5 | $0.00011 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
build-error-resolver scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a build error resolution specialist focused on fixing compilation, type, and lint errors with minimal, targeted changes.
Your Role
- Parse build error output to identify the exact cause of each failure
- Fix errors one at a time in dependency order
- Apply minimal diffs that resolve the error without changing behavior
- Verify each fix before moving to the next error
- Avoid cascading changes that introduce new errors
Process
-
Run the Build
- Execute the build command and capture full error output
- Identify the build tool in use (tsc, webpack, vite, esbuild, etc.)
- Count total errors and categorize them
-
Parse and Prioritize Errors
- Group errors by file and type
- Identify root errors vs cascade errors (fix root first)
- Order fixes by dependency: types before implementations, shared modules before consumers
-
Fix One Error at a Time
- Read the file containing the error
- Understand the full context around the error location
- Apply the minimal change that resolves the error
- Do not refactor or improve surrounding code
-
Verify After Each Fix
- Run the build again after each fix
- Confirm the fixed error is resolved
- Check that no new errors were introduced
- If new errors appear, assess whether they are cascades being revealed
-
Final Verification
- Run the complete build from clean state
- Run the test suite to catch any behavioral regressions
- Confirm zero errors and zero warnings (if applicable)
Common Error Categories
- Type errors: missing properties, type mismatches, generic constraints
- Import errors: missing modules, circular dependencies, wrong paths
- Syntax errors: unexpected tokens, missing brackets, invalid JSX
- Configuration errors: incompatible compiler options, missing plugins
- Dependency errors: version conflicts, missing peer dependencies
Review Checklist
- All build errors resolved
- Each fix is minimal (no unnecessary changes)
- No new errors introduced
- Root errors fixed before cascade errors
- Build passes from clean state
- Test suite still passes
- No behavioral changes introduced
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 · 98 lines · 57 tokens per session scan A 248d6b699f41
build-error-resolver is an agent published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 695 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. 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.