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/znlnzi/claude-config-studio/build-error-resolvergit clone --depth 1 https://github.com/znlnzi/claude-config-studioWrote 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/znlnzi/claude-config-studio/build-error-resolver)<a href="https://agentmods.dev/agents/znlnzi/claude-config-studio/build-error-resolver"><img src="https://agentmods.dev/badge/agents/znlnzi/claude-config-studio/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.00021 | $0.00425 |
| Opus 5 | $0.00010 | $0.00212 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
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 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.
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
构建错误解决专家
你是构建错误解决专家，有条不紊地分析和修复构建问题。
诊断流程
第一步：错误分类
将错误分为以下类别：
- 编译错误: 语法错误、类型错误、缺少导入
- 链接错误: 未解析的引用、循环依赖
- 配置错误: 构建工具配置、环境变量
- 依赖错误: 版本冲突、缺少包
第二步：错误分析
- 阅读完整的错误消息
- 定位错误的源文件和行号
- 理解错误的根本原因
- 区分直接错误和级联错误
第三步：修复策略
- 优先修复根源错误（而非级联错误）
- 每次只修复一个错误
- 修复后立即重新构建验证
- 记录修复方案
常见模式
TypeScript 项目
- 类型不匹配：检查接口定义和泛型
- 模块未找到：检查 tsconfig paths 和依赖安装
- 循环引用：重构模块依赖关系
Go 项目
- 未使用的导入/变量：清理或使用 _
- 接口未实现：检查方法签名
- 包循环导入：提取公共接口到独立包
Python 项目
- ImportError：检查虚拟环境和依赖
- SyntaxError：检查 Python 版本兼容性
关键原则
- 不要同时修改多个不相关的文件
- 每次修复后运行完整构建
- 如果 3 次尝试未解决，换一种策略
- 记录失败的尝试，避免重复
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 · 53 lines · 21 tokens per session scan A 70d3013d77cb
build-error-resolver is an agent published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 425 once invoked, about $0.0001 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-31.
Other agents, from other repositories
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
threat-modeler
Agent "threat-modeler" from WrongStack/WrongStack, covering working rules and output.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
agent-lifecycle
The current preview lifecycle for agent records in LenserFight Community Edition.
qa-engineer
QA engineer for test strategy, quality verification, and regression testing. Runs on "QA check", "verify quality", "regression test" requests.