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/diet103/claude-code-infrastructure-showcase/auto-error-resolvergit clone --depth 1 https://github.com/diet103/claude-code-infrastructure-showcaseWhat 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.00011 | $0.00784 |
| Opus 5 | $0.00005 | $0.00392 |
| Sonnet 5 | $0.00002 | $0.00157 |
| Haiku 4.5 | $0.00001 | $0.00078 |
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 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.
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 Copies of this mod
1 near-identical copy found in the catalogue:
- auto-error-resolver — 86% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 95 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 your project uses a process manager:
- Check logs for the affected service to see runtime errors
- Look for error log files in the service directory
-
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
Example Workflow:
# 1. Read error information
cat ~/.claude/tsc-cache/*/last-errors.txt
# 2. Check which TSC commands to use
cat ~/.claude/tsc-cache/*/tsc-commands.txt
# 3. Identify the file and error
# Error: src/components/Button.tsx(10,5): error TS2339: Property 'onClick' does not exist on type 'ButtonProps'.
# 4. Fix the issue
# (Edit the ButtonProps interface to include onClick)
# 5. Verify the fix using the correct command from tsc-commands.txt
cd ./frontend && npx tsc --project tsconfig.app.json --noEmit
# For backend repos:
cd ./backend && npx tsc --noEmit
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 · 95 lines · 11 tokens per session scan B e78c854b7dcc
auto-error-resolver is an agent published in the GitHub repository diet103/claude-code-infrastructure-showcase (10,016 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 784 once invoked, about $0.0001 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
code-style
Agent "code-style" from callstack/react-native-testing-library, covering typescript and code style, linting and formatting and imports.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
ts-coder
Use this agent when you need to write or refactor TypeScript code following strict type safety and simplicity principles. This includes creating type definitions, implementing business logic, refactoring JavaScript to TypeScript, or optimizing type inference.
typescript-pro
Write idiomatic TypeScript with advanced type system features, strict typing, and modern patterns. Masters generic constraints, conditional types, and type inference. Use PROACTIVELY for TypeScript optimization, complex types, or migration from JavaScript.
node-developer
Senior Node.js/TypeScript Developer specialized in small dashboards and web apps where a full .NET stack would be overkill. Expert in TypeScript, Next.js (full-stack React), Node services, and the modern Node tooling ecosystem.
typescript-dev
Expert TypeScript development agent for any TypeScript codebase. Use this agent whenever the task involves writing, modifying, debugging, refactoring, or reviewing TypeScript — implementing features, fixing type errors or tsconfig problems, resolving ESLint findings, writing tests, designing library APIs, Node backend…