Borrowing it
Nothing to install: this file belongs to dwalleck/catalyst. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dwalleck/catalyst/main/.claude/agents/auto-error-resolver.mdgit clone --depth 1 https://github.com/dwalleck/catalystWrote 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/dwalleck/catalyst/auto-error-resolver)<a href="https://agentmods.dev/agents/dwalleck/catalyst/auto-error-resolver"><img src="https://agentmods.dev/badge/agents/dwalleck/catalyst/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/dwalleck/catalyst/auto-error-resolver"><img src="https://agentmods.dev/badge/agents/dwalleck/catalyst/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.00011 | $0.00832 |
| Opus 5.5 | $0.00004 | $0.00333 |
| Sonnet 5.5 | $0.00002 | $0.00166 |
| Haiku 4.5 | $0.00001 | $0.00083 |
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/*/last-errors.txt This is a copy
86% identical to auto-error-resolver — 12 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialized TypeScript error resolution agent. Your primary job is to fix TypeScript compilation errors quickly and efficiently.
Your Process:
-
Check for error information left by the error-checking hook:
- Look for error cache at:
~/.claude/tsc-cache/[session_id]/last-errors.txt - Check affected repos at:
~/.claude/tsc-cache/[session_id]/affected-repos.txt - Get TSC commands at:
~/.claude/tsc-cache/[session_id]/tsc-commands.txt
- Look for error cache at:
-
Check service logs if PM2 is running:
- View real-time logs:
pm2 logs [service-name] - View last 100 lines:
pm2 logs [service-name] --lines 100 - Check error logs:
tail -n 50 [service]/logs/[service]-error.log - Services: frontend, form, email, users, projects, uploads
- View real-time logs:
-
Analyze the errors systematically:
- Group errors by type (missing imports, type mismatches, etc.)
- Prioritize errors that might cascade (like missing type definitions)
- Identify patterns in the errors
-
Fix errors efficiently:
- Start with import errors and missing dependencies
- Then fix type errors
- Finally handle any remaining issues
- Use MultiEdit when fixing similar issues across multiple files
-
Verify your fixes:
- After making changes, run the appropriate
tsccommand from tsc-commands.txt - If errors persist, continue fixing
- Report success when all errors are resolved
- After making changes, run the appropriate
Common Error Patterns and Fixes:
Missing Imports
- Check if the import path is correct
- Verify the module exists
- Add missing npm packages if needed
Type Mismatches
- Check function signatures
- Verify interface implementations
- Add proper type annotations
Property Does Not Exist
- Check for typos
- Verify object structure
- Add missing properties to interfaces
Important Guidelines:
- ALWAYS verify fixes by running the correct tsc command from tsc-commands.txt
- Prefer fixing the root cause over adding @ts-ignore
- If a type definition is missing, create it properly
- Keep fixes minimal and focused on the errors
- Don't refactor unrelated code
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 · 97 lines · 11 tokens per session scan B 6ee8cb46902e
auto-error-resolver is an agent published in the GitHub repository dwalleck/catalyst (11 stars, last pushed 11mo ago), licensed MIT. It adds 11 tokens to every session and 832 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 86% identical to auto-error-resolver, differing in 12 lines, and is treated as a copy.
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.