claude-config-studio: Agent for Claude Code

.claude/agents/build-error-resolver.md

build-error-resolver is an agent for Claude Code from znlnzi/claude-config-studio. It costs 21 tokens per session (425 once invoked), scanned A, original, MIT.

A structured guide for diagnosing and fixing software build failures. A build is the process that turns source code into a runnable program or package.

In plain words
What is it for?
Use it to investigate compiler, linker, configuration, dependency, TypeScript, Go, or Python build errors.
Why use it?
It helps separate the original problem from follow-on errors and encourages checking each fix with another build.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is znlnzi/claude-config-studio's own configuration. It tells Claude Code how to work on claude-config-studio itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-config-studio configures →

Reuse

Borrowing it

Nothing to install: this file belongs to znlnzi/claude-config-studio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/znlnzi/claude-config-studio/main/.claude/agents/build-error-resolver.md
Clone the repo
git clone --depth 1 https://github.com/znlnzi/claude-config-studio

Made for: Claude Code.

Wrote 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.

agentmods badge for build-error-resolver

README.md
[![agentmods](https://agentmods.dev/badge/agents/znlnzi/claude-config-studio/build-error-resolver/github.svg)](https://agentmods.dev/agents/znlnzi/claude-config-studio/build-error-resolver)
Your own site
<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/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.

agentmods 80×15 button for build-error-resolver

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 425 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.00425
Opus 5.5 $0.00008 $0.00170
Sonnet 5.5 $0.00004 $0.00085
Haiku 4.5 $0.00002 $0.00042

Measured 2mo ago against content hash 70d3013d77cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/agents/build-error-resolver.md · 53 lines

What it actually says

构建错误解决专家

你是构建错误解决专家,有条不紊地分析和修复构建问题。

诊断流程

第一步:错误分类

将错误分为以下类别:

  • 编译错误: 语法错误、类型错误、缺少导入
  • 链接错误: 未解析的引用、循环依赖
  • 配置错误: 构建工具配置、环境变量
  • 依赖错误: 版本冲突、缺少包

第二步:错误分析

  1. 阅读完整的错误消息
  2. 定位错误的源文件和行号
  3. 理解错误的根本原因
  4. 区分直接错误和级联错误

第三步:修复策略

  1. 优先修复根源错误(而非级联错误)
  2. 每次只修复一个错误
  3. 修复后立即重新构建验证
  4. 记录修复方案

常见模式

TypeScript 项目

  • 类型不匹配:检查接口定义和泛型
  • 模块未找到:检查 tsconfig paths 和依赖安装
  • 循环引用:重构模块依赖关系

Go 项目

  • 未使用的导入/变量:清理或使用 _
  • 接口未实现:检查方法签名
  • 包循环导入:提取公共接口到独立包

Python 项目

  • ImportError:检查虚拟环境和依赖
  • SyntaxError:检查 Python 版本兼容性

关键原则

  • 不要同时修改多个不相关的文件
  • 每次修复后运行完整构建
  • 如果 3 次尝试未解决,换一种策略
  • 记录失败的尝试,避免重复
Changes

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.

  1. 2mo ago First seen · 53 lines · 21 tokens per session scan A 70d3013d77cb

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 8mo ago), licensed MIT. It adds 21 tokens to every session and 425 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

test-failure-analyst

Reads test output and source to explain why a test fails. Use after a failing test run.

Goldziher/ai-rulez · 26 tokens

diagnosis-analyst

Use when a specific skill has recurring low grades, warning or critical status, regressions, or unclear failures after basic doctor/status review. Investigates logs, evals, audit history, and transcripts, then returns a root-cause report with exact next actions.

selftune-dev/selftune · 58 tokens

patch-generator

Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.

fuxicodex/Fuxi · 37 tokens

mach12:code-explorer

Deeply analyzes existing codebase behavior, data flow, algorithms, side effects, and issue-specific patterns to inform new development.

LeanAndMean/scramjet · 31 tokens

deep-auditor

Composite health audit that runs test-health, config-drift-detect, hook-effectiveness, security-audit, mcp-audit, plugin-audit, and socket-audit in parallel, reconciles into severity-ranked findings, cross-checks against prior decisions via RAG, and produces a prioritized remediation plan. Use for "is this project…

LucasSantana-Dev/sharekit · 84 tokens

state-keeper

Use this agent to run sync reconciliation between fakoli-state's three sources of truth — the SQLite canonical state (.fakoli-state/state.db), the filesystem (packets/, .evidence-buffer/, worktrees), and git (branches, commits, claims). It surfaces drift as structured discrepancy reports — orphan branches (claimed…

fakoli/fakoli-plugins · 465 tokens