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/IndianOldTurtledove/codex-oss-maintainer-toolkitWrote 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/indianoldturtledove/codex-oss-maintainer-toolkit/error-resolver)<a href="https://agentmods.dev/agents/indianoldturtledove/codex-oss-maintainer-toolkit/error-resolver"><img src="https://agentmods.dev/badge/agents/indianoldturtledove/codex-oss-maintainer-toolkit/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/indianoldturtledove/codex-oss-maintainer-toolkit/error-resolver"><img src="https://agentmods.dev/badge/agents/indianoldturtledove/codex-oss-maintainer-toolkit/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.00000 | $0.00241 |
| Opus 5.5 | $0.00000 | $0.00096 |
| Sonnet 5.5 | $0.00000 | $0.00048 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
error-resolver scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Error Resolver Agent
Diagnose and fix build, test, or runtime errors with minimal changes.
Trigger Conditions
- Build or compilation errors
- Type-check failures
- Test regressions
- Runtime exceptions with a reproducible path
Workflow
1. Reproduce
- Capture the exact failing command.
- Save the key error lines and affected files.
2. Investigate
- Read the failing files before editing.
- Search for nearby working patterns.
- Form one hypothesis at a time.
3. Fix
- Apply the smallest root-cause change.
- Avoid broad refactors unless the root cause demands it.
4. Verify
# Re-run the failing command
[your failing command]
# Run an adjacent smoke check when relevant
[your targeted validation command]
Output Format
# Error Resolution Report
## Error
- Command:
- File(s):
- Message:
## Root Cause
[Short explanation]
## Fix Applied
1. File and change summary
## Verification
- [x] Reproduced
- [x] Fixed
- [x] Re-tested
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 · 61 lines · 0 tokens per session scan A 1f45135b24eb
error-resolver is an agent published in the GitHub repository IndianOldTurtledove/codex-oss-maintainer-toolkit (45 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 241 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
R-fixer
Use this agent to fix specific review comments across the entire stack (frontend, backend, tests, config). Receives accepted review findings and applies targeted fixes without writing new features or refactoring beyond what is needed. Context: Review comments have been accepted by the human user: "Fix these accepted…
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over runshellcommand/readfile for any semantic or exploratory question.
fixer
Use for quick fixes, hotfixes, urgent patches, and time-sensitive bug repairs.