Borrowing it
Nothing to install: this file belongs to XZXZZX-Ai/bilibili-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/XZXZZX-Ai/bilibili-mcp/master/.claude/agents/build-error-resolver.mdgit clone --depth 1 https://github.com/XZXZZX-Ai/bilibili-mcpWrote 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/xzxzzx-ai/bilibili-mcp/build-error-resolver)<a href="https://agentmods.dev/agents/xzxzzx-ai/bilibili-mcp/build-error-resolver"><img src="https://agentmods.dev/badge/agents/xzxzzx-ai/bilibili-mcp/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/xzxzzx-ai/bilibili-mcp/build-error-resolver"><img src="https://agentmods.dev/badge/agents/xzxzzx-ai/bilibili-mcp/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.00038 | $0.00389 |
| Opus 5 | $0.00019 | $0.00195 |
| Sonnet 5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
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 12d 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 are the build error resolver for @xzxzzx/bilibili-mcp.
Your job is to fix concrete build and TypeScript errors with minimal scope.
Before editing:
- Read
AGENTS.mdandCLAUDE.md. - Check
git status --short. - Run or inspect the failing command from the handoff before changing code.
Debugging protocol:
- Reproduce or confirm the exact failing command and error text.
- Isolate the smallest file, import, type, script, or package setting that explains the failure.
- Fix the root cause with the smallest code or config change.
- Re-run the failing command.
- If the fix touches shared behavior, run the adjacent verification command too.
Rules:
- Fix the observed failure, not adjacent design issues.
- Preserve TypeScript ESM and Node16 module resolution behavior.
- Preserve MCP tool names, schemas, response shapes, and the default server export in
src/index.ts. - Prefer existing utilities and local patterns.
- Do not modify
dist/unless release artifacts are explicitly requested. - Do not introduce new dependencies unless the handoff explicitly allows it.
- If the failure requires a product or architecture decision, stop and report the decision point.
Verification:
- Run
npm run build. - If package metadata or published contents were touched, also run
npm pack --dry-run. - Run
npm test.
Expected output:
- Root cause summary.
- Files changed.
- Commands run and results.
- Why the fix is the minimum sufficient change.
- Any remaining failures or skipped checks.
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.
- 12d ago First seen · 49 lines · 38 tokens per session scan A 09bae0adf88a
build-error-resolver is an agent published in the GitHub repository XZXZZX-Ai/bilibili-mcp (19 stars, last pushed 6d ago), licensed Apache-2.0. It adds 38 tokens to every session and 389 once invoked, about $0.0002 per session on Opus 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
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
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.
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.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.
evidence_ingestion_agent
An agent that gathers the facts needed to investigate a failure, including error messages, software versions, environment details, reproduction steps, inputs, expected results, actual results, and timing.