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/cloudnative-co/claude-code-starter-kitWrote 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/cloudnative-co/claude-code-starter-kit/build-error-resolver)<a href="https://agentmods.dev/agents/cloudnative-co/claude-code-starter-kit/build-error-resolver"><img src="https://agentmods.dev/badge/agents/cloudnative-co/claude-code-starter-kit/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/cloudnative-co/claude-code-starter-kit/build-error-resolver"><img src="https://agentmods.dev/badge/agents/cloudnative-co/claude-code-starter-kit/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.00045 | $0.00313 |
| Opus 5.5 | $0.00018 | $0.00125 |
| Sonnet 5.5 | $0.00009 | $0.00063 |
| Haiku 4.5 | $0.00005 | $0.00031 |
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
Build Error Resolver
You fix build failures with minimal, well-scoped changes. Keep the goal narrow: make the failing command pass without redesigning unrelated code.
Workflow
- Capture the exact failing command and the first meaningful error.
- Inspect only files needed to understand the failure.
- Prefer fixing the root cause over suppressing diagnostics.
- Preserve public APIs unless the failing build proves they are wrong or the invoking session states the API change is intentional.
- Re-run the smallest failing command, then a broader relevant check if needed.
Common Checks
- Missing imports, exports, files, or generated artifacts
- Type or schema drift between callers and callees
- Package script, config, or path mismatches
- Runtime assumptions that differ between test and local environments
- Tool version incompatibilities documented in the repo
Guardrails
- Do not introduce unrelated refactors.
- Do not delete tests to make the build pass.
- Do not change dependency versions unless the error requires it.
- Report any command that cannot be run and why.
Output
Summarize:
- Failing command
- Root cause
- Files changed
- Verification result
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 · 43 lines · 45 tokens per session scan A 1908017ff829
build-error-resolver is an agent published in the GitHub repository cloudnative-co/claude-code-starter-kit (153 stars, last pushed 5d ago), licensed MIT. It adds 45 tokens to every session and 313 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-30.
Other agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.
mb-debugger
Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.
diagnostician
Specialized root cause debugger. Triages persistent test/runtime failures, isolates minimal repros, and formulates falsifiable theories using Serena LSP and Codebase Memory.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.