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/cyvid7-darus10/claude-code-config/build-error-resolvergit clone --depth 1 https://github.com/Cyvid7-Darus10/claude-code-configWrote 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/cyvid7-darus10/claude-code-config/build-error-resolver)<a href="https://agentmods.dev/agents/cyvid7-darus10/claude-code-config/build-error-resolver"><img src="https://agentmods.dev/badge/agents/cyvid7-darus10/claude-code-config/build-error-resolver.svg" alt="Measured on agentmods" 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 | $0.00050 | $0.00910 |
| Opus 5 | $0.00025 | $0.00455 |
| Sonnet 5 | $0.00010 | $0.00182 |
| Haiku 4.5 | $0.00005 | $0.00091 |
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 This is a copy
98% identical to build-error-resolver — 6 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 — 115 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 · 115 lines · 50 tokens per session scan C 28597d1e97a6
build-error-resolver is an agent published in the GitHub repository Cyvid7-Darus10/claude-code-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 910 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 98% identical to build-error-resolver, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
changelog-archival
Agent "changelog-archival" from doobidoo/MCP-Context-Provider, covering changelog archival agent, when to use, workflow, 1. analyze current state and 2. determine archive target.
instructions
In conversational responses only, use a laid-back California surfer vibe from the 60s–80s. Address the user as Boss.
code-reviewer
Expert code review specialist. Proactively reviews code for quality, security, and maintainability with heightened attention on configuration drift that could impact production reliability. Invoke immediately after code or config changes to prevent regressions.
calibration-planner
Writes and updates plan.md for a calibration run. Two modes: init (creates the run folder, writes the skeleton plan.md, records the intent) and improve (reads the evaluator's baseline reports, groups findings by pattern signature for the recurrence detector, and emits a prioritised improvement plan with kind: edit…
calibration-feature-evaluator
Per-feature worker for the calibration evaluator's parallel fan-out. Audits exactly one Claude Code feature (claude-md | rules | settings | skills | subagents | hooks | mcp | plugins | general) against its bundle's reference.md + scripts/, writes a slim draft section to /.drafts/feat- .md, and returns one summary…
calibration-flow-evaluator
Behavioural worker for the /calibration-flow flow. Drives a named workflow-under-test over a case set of golden fixtures, records the findings it produces, diffs them against each case's expected.md oracle via the deterministic score-flow.sh, and writes eval-flow- .md (node recall/precision, edge handoff contracts…