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.
npx agentmods add agents/sejongjeong/runai-mcp/build-error-resolvergit clone --depth 1 https://github.com/sejongjeong/runai-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/sejongjeong/runai-mcp/build-error-resolver)<a href="https://agentmods.dev/agents/sejongjeong/runai-mcp/build-error-resolver"><img src="https://agentmods.dev/badge/agents/sejongjeong/runai-mcp/build-error-resolver.svg" alt="Measured on agentmods" 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.00050 | $0.00910 |
| Opus 5 | $0.00025 | $0.00455 |
| Sonnet 5 | $0.00010 | $0.00182 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade C, and why
build-error-resolver scanned grade C with 1 finding 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .next node_modules/.cache && npm run build The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 5d ago First seen · 115 lines · 50 tokens per session scan C 28597d1e97a6
build-error-resolver is an agent published in the GitHub repository sejongjeong/runai-mcp (0 stars, last pushed 5mo ago), with no licence file. It adds 50 tokens to every session and 910 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
build-error-resolver
构建与 TypeScript 错误修复专家。当构建失败或出现类型错误时，请主动（PROACTIVELY）使用。仅修复构建/类型错误，保持最小差异（diff），不进行架构性修改。重点是快速使构建通过（get the build green）。.
build-expert
PROACTIVELY invoke when: tsconfig compilation fails, module resolution breaks, build performance degrades, monorepo project references need wiring, or build tool (tsc/esbuild/swc/Rollup/Webpack/Vite) TS integration is misconfigured.
type-expert
PROACTIVELY activate when encountering complex generic constraints, conditional/mapped/template literal/recursive type errors, brand type design, or type-checking performance issues. Specializes in type-level programming and TS error resolution.
cli-expert
PROACTIVELY activate for CLI tool development, npm binary issues, command-line argument parsing, cross-platform CLI compatibility, and monorepo CLI detection problems.