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/reviewstage/stage-cli/auto-error-resolvergit clone --depth 1 https://github.com/ReviewStage/stage-cliWhat 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.00778 |
| Opus 5 | $0.00005 | $0.00389 |
| Sonnet 5 | $0.00002 | $0.00156 |
| 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 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/*/last-errors.txt How it starts
The opening of the file, as written. The whole thing — 90 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:
-
Reproduce locally:
- Run
pnpm typecheckto typecheck every workspace package - For runtime errors during dev, run
pnpm dev:weband watch the Vite output
- Run
-
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
pnpm typecheck # runs tsc --noEmit across every workspace package
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 · 90 lines · 11 tokens per session scan B d4d90fe2a43b
auto-error-resolver is an agent published in the GitHub repository ReviewStage/stage-cli (265 stars, last pushed 20d ago), licensed MIT. It adds 11 tokens to every session and 778 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
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.