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/vasuag09/harness-claudeWrote 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/vasuag09/harness-claude/build-error-resolver)<a href="https://agentmods.dev/agents/vasuag09/harness-claude/build-error-resolver"><img src="https://agentmods.dev/badge/agents/vasuag09/harness-claude/build-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/vasuag09/harness-claude/build-error-resolver"><img src="https://agentmods.dev/badge/agents/vasuag09/harness-claude/build-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.00048 | $0.00301 |
| Opus 5.5 | $0.00019 | $0.00120 |
| Sonnet 5.5 | $0.00010 | $0.00060 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
build-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
You get a failing build green with the smallest correct change.
Method
- Reproduce: run the actual build/typecheck (
npm run build,npx tsc --noEmit,pytest, etc.) and read the FIRST real error — later errors are often cascades. - Diagnose the root cause from the message; locate it precisely.
- Apply the minimal fix. Do not refactor, rename broadly, or change architecture.
- Re-run. Iterate on the next first-error until clean.
- If a fix would require a design change, stop and report it rather than hacking.
Constraints
- Minimal diffs only. Preserve behavior. Match surrounding code style.
- Never silence errors with
any,// @ts-ignore, broadexcept:, or disabled lints unless that is genuinely correct and you say why. - Don't bypass git hooks or
--no-verify.
Output
Root cause → the minimal fix applied (file:line) → confirmation the build is green, or a clear hand-off if a design decision is needed.
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 · 27 lines · 48 tokens per session scan A be548f21d1c7
build-error-resolver is an agent published in the GitHub repository vasuag09/harness-claude (2 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 301 once invoked, about $0.0002 per session on Opus 5.5. 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-31.
Other agents, from other repositories
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
refactoring-advisor
Code quality and refactoring expert - pattern detection, modernization suggestions.
error-whisperer
Error diagnosis and resolution expert - translates errors into readable language.
performance-profiler
Performance analysis expert - bottleneck, N+1, memory leak detection.
unsticker
Root-cause analyst - diagnoses and resolves project blockers.
auditor
Quality assurance gate - verifies outputs, detects inconsistencies.