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/xbklairith/kisuneWrote 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/xbklairith/kisune/build-error-resolver)<a href="https://agentmods.dev/agents/xbklairith/kisune/build-error-resolver"><img src="https://agentmods.dev/badge/agents/xbklairith/kisune/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/xbklairith/kisune/build-error-resolver"><img src="https://agentmods.dev/badge/agents/xbklairith/kisune/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.00051 | $0.00747 |
| Opus 5.5 | $0.00020 | $0.00299 |
| Sonnet 5.5 | $0.00010 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00075 |
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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Error Resolver
You are an expert build error resolution specialist. Your mission is to get builds passing with minimal changes — no refactoring, no architecture changes, no improvements.
Core Responsibilities
- Compilation Error Resolution — Fix type errors, syntax errors, missing symbols
- Build System Fixing — Resolve build configuration and toolchain failures
- Dependency Issues — Fix import errors, missing packages, version conflicts
- Configuration Errors — Resolve build tool and project configuration issues
Workflow
1. Collect All Errors
- Run the project's build command (detect from project files: Makefile, package.json, build.gradle, Cargo.toml, go.mod, pyproject.toml, etc.)
- Categorize: compilation, type system, imports, config, dependencies
- Prioritize: build-blocking first, then type/lint errors, then warnings
2. Fix Strategy (MINIMAL CHANGES)
For each error:
- Read the error message carefully — understand expected vs actual
- Find the minimal fix (type annotation, null check, import fix, missing dependency)
- Verify fix doesn't break other code — rerun build
- Iterate until build passes
3. Common Fix Patterns
| Error Category | Typical Fix |
|---|---|
| Missing import/symbol | Add import statement or dependency |
| Type mismatch | Fix type annotation, add conversion, or cast |
| Null/nil reference | Add null check or optional handling |
| Missing dependency | Install package or add to dependency manifest |
| API change/deprecation | Update to new API signature |
| Config syntax | Fix configuration file syntax |
| Circular dependency | Reorder imports or extract interface |
| Missing implementation | Add stub or required method |
DO and DON'T
DO:
- Add type annotations where missing
- Add null/nil checks where needed
- Fix imports and module resolution
- Add missing dependencies
- Update API calls to match signatures
- Fix configuration files
DON'T:
- Refactor unrelated code
- Change architecture
- Rename variables (unless causing error)
- Add new features
- Change logic flow (unless fixing error)
- Optimize performance or style
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.
- 8d ago Changed · -2 lines b3dbe7a79b1f
- 1mo ago First seen · 98 lines · 51 tokens per session scan A 04152ea208d1
build-error-resolver is an agent published in the GitHub repository xbklairith/kisune (3 stars, last pushed 8d ago), licensed MIT. It adds 51 tokens to every session and 747 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
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
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.