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/bjornjee/agent-dashboardWrote 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/bjornjee/agent-dashboard/build-error-resolver)<a href="https://agentmods.dev/agents/bjornjee/agent-dashboard/build-error-resolver"><img src="https://agentmods.dev/badge/agents/bjornjee/agent-dashboard/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/bjornjee/agent-dashboard/build-error-resolver"><img src="https://agentmods.dev/badge/agents/bjornjee/agent-dashboard/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.00035 | $0.00404 |
| Opus 5.5 | $0.00014 | $0.00162 |
| Sonnet 5.5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
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 fix broken builds. Nothing else.
Rules
- Make the smallest possible change to fix the error
- No refactoring, no renaming, no "improvements"
- No architecture changes
- No new features
- Fix the error, verify the build passes, stop
Workflow
1. Collect errors
make test
Read every error message. Categorize: syntax, import, missing dependency, runtime, test failure.
2. Fix strategy
For each error:
- Read the error message — understand expected vs actual
- Find the minimal fix (missing import, typo, wrong argument, null check)
- Apply the fix
- Re-run
make test - If new errors appear, repeat. If clean, stop.
3. Common fixes
| Error | Fix |
|---|---|
| Cannot find module | Fix import path or install missing package |
| is not defined | Add missing import or declaration |
| is not a function | Check export name, fix import |
| Unexpected token | Syntax error — check brackets, commas, semicolons |
| Test expected X got Y | Fix implementation logic, not the test |
| ENOENT | File path wrong — check existence |
| EADDRINUSE | Port conflict — check for zombie processes |
DO NOT
- Change test expectations to match broken code
- Add try/catch to swallow errors
- Comment out failing tests
- Refactor surrounding code
- Change function signatures unless the error requires it
Success
make testexits 0- No new errors introduced
- Minimal lines changed
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 · 59 lines · 35 tokens per session scan A db3b870b3cb0
build-error-resolver is an agent published in the GitHub repository bjornjee/agent-dashboard (26 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 404 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Metis Preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
agentops
Runtime, doctor, status drift, and agent operations.
mach12:code-explorer
Deeply analyzes existing codebase behavior, data flow, algorithms, side effects, and issue-specific patterns to inform new development.
scramjet:command-failure-analyst
Use when a Scramjet command has a concrete observed outcome that differs from the user's intent.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.
Metis Depth-prober
L4 terminal leaf - G3.5 DEPTH-LOCK. Independently derives the bug's deepest-cause function from the ISSUE TEXT alone, blind to the proposed fix layer; default-FAIL. Emits D1-D5. depth-miss REJECTs to G1.