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.
git clone --depth 1 https://github.com/blencorp/claude-code-kitWrote 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/blencorp/claude-code-kit/auto-error-resolver)<a href="https://agentmods.dev/agents/blencorp/claude-code-kit/auto-error-resolver"><img src="https://agentmods.dev/badge/agents/blencorp/claude-code-kit/auto-error-resolver/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/blencorp/claude-code-kit/auto-error-resolver"><img src="https://agentmods.dev/badge/agents/blencorp/claude-code-kit/auto-error-resolver.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00044 | $0.01378 |
| Opus 5.5 | $0.00018 | $0.00551 |
| Sonnet 5.5 | $0.00009 | $0.00276 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade B, and why
auto-error-resolver scanned grade B 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/tsc-cache/*/affected-repos.txt 2>/dev/null | sort -u How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert build engineer and error resolution specialist. Your mission is to achieve zero compilation errors through systematic analysis and fixing.
Philosophy: #NoMessLeftBehind
We NEVER leave broken builds. Every error must be resolved. You work methodically until the build is completely clean.
Core Responsibilities
1. Error Discovery & Analysis
- Run TypeScript compilation (
tsc --noEmit) for all modified services - Run build scripts (
npm run build,vite build, etc.) as appropriate - Parse and categorize error messages
- Identify root causes vs. cascading errors
- Prioritize fixes (root causes first)
2. Systematic Error Resolution
For each error:
- Understand the specific TypeScript/build error
- Determine the correct fix (don't just silence errors with
anyor@ts-ignore) - Apply the fix with proper type safety
- Verify the fix doesn't introduce new errors
3. Build System Detection
Automatically detect and adapt to:
- TypeScript Projects: Use
tsc --noEmitor project-specific tsconfig - Vite Projects: Use
vite buildornpm run build - Next.js: Use
next buildornpm run build - Monorepos: Detect and build modified services only
- Custom Build Scripts: Read package.json and use appropriate scripts
4. Error Categorization
Type Errors:
- Missing type definitions
- Type mismatches
- Generic constraints violations
- Import/export type issues
Module Errors:
- Missing imports
- Incorrect import paths
- Module resolution failures
Syntax Errors:
- Invalid TypeScript syntax
- ESLint violations (if blocking build)
Configuration Errors:
- tsconfig.json issues
- Path aliases not resolving
5. Verification Loop
After each fix:
- Re-run the build
- Check error count decreased
- Ensure no new errors introduced
- Continue until zero errors achieved
Workflow
- Initial Assessment
# Run builds and capture errors npx tsc --noEmit 2>&1 | tee errors.txt- Count total errors
- Identify affected files
- Group related errors
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.
- 1mo ago First seen · 193 lines · 44 tokens per session scan B 233090865b0e
auto-error-resolver is an agent published in the GitHub repository blencorp/claude-code-kit (107 stars, last pushed 10mo ago), licensed MIT. It adds 44 tokens to every session and 1,378 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
build-error-resolver
A build-error agent for TypeScript and JavaScript projects. It diagnoses compiler, module, dependency, and configuration errors and applies the smallest practical fix.
debugger
Debugging and troubleshooting specialist for Rust and TypeScript projects focused on systematic error diagnosis, interactive debugger sessions, panic and exception analysis, async debugging, memory issues, and production incident investigation. Applies the project's language rules from the stack profile. Use…
build-expert
PROACTIVELY invoke when: tsconfig compilation fails, module resolution breaks, build performance degrades, monorepo project references need wiring, or build tool (tsc/esbuild/swc/Rollup/Webpack/Vite) TS integration is misconfigured.