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/blencorp/claude-code-kit/auto-error-resolvergit clone --depth 1 https://github.com/blencorp/claude-code-kitWhat 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.00044 | $0.01378 |
| Opus 5 | $0.00022 | $0.00689 |
| Sonnet 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 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.
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.
- 2d 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 (101 stars, last pushed 9mo ago), licensed MIT. It adds 44 tokens to every session and 1,378 once invoked, about $0.0002 per session on Opus 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.