everything-claude-code: Agent for Claude Code

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

build-error-resolver is an agent for Claude Code, Kiro from mit-network/everything-claude-code. It costs 50 tokens per session (898 once invoked), scanned C, a copy of build-error-resolver, MIT.

A specialist for resolving build and TypeScript errors with the smallest necessary code changes. TypeScript is JavaScript with checks that catch many mistakes before the program runs.

In plain words
What is it for?
Use it to diagnose compilation failures, type errors, missing imports or packages, dependency conflicts, and configuration problems, then verify the fix with builds and checks.
Why use it?
It helps turn a failing build into a passing one without introducing unrelated refactoring or architectural changes.

Agent for Claude CodeKiro

Written for Claude Code and Kiro: shipped in a Claude Code plugin, but also installed under .kiro/.

This is mit-network/everything-claude-code's own configuration. It tells Claude Code and Kiro how to work on everything-claude-code 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 everything-claude-code configures →

Part of the everything-claude-code plugin — 39 skills, 3 commands, 16 agents shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to mit-network/everything-claude-code. 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/mit-network/everything-claude-code/main/.kiro/agents/build-error-resolver.md
Clone the repo
git clone --depth 1 https://github.com/mit-network/everything-claude-code

Made for: Claude Code, Kiro.

Or install everything-claude-code, the plugin that ships this one along with the rest of its 39 skills, 3 commands, 16 agents.

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/mit-network/everything-claude-code/build-error-resolver/github.svg)](https://agentmods.dev/agents/mit-network/everything-claude-code/build-error-resolver)
Your own site
<a href="https://agentmods.dev/agents/mit-network/everything-claude-code/build-error-resolver"><img src="https://agentmods.dev/badge/agents/mit-network/everything-claude-code/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/mit-network/everything-claude-code/build-error-resolver"><img src="https://agentmods.dev/badge/agents/mit-network/everything-claude-code/build-error-resolver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 898 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00050 $0.00898
Opus 5.5 $0.00020 $0.00359
Sonnet 5.5 $0.00010 $0.00180
Haiku 4.5 $0.00005 $0.00090

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

Security

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 1mo 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
Origin

This is a copy

100% identical to build-error-resolver — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.kiro/agents/build-error-resolver.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 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

  1. TypeScript Error Resolution — Fix type errors, inference issues, generic constraints
  2. Build Error Fixing — Resolve compilation failures, module resolution
  3. Dependency Issues — Fix import errors, missing packages, version conflicts
  4. Configuration Errors — Resolve tsconfig, webpack, Next.js config issues
  5. Minimal Diffs — Make smallest possible changes to fix errors
  6. No Architecture Changes — Only fix errors, don't redesign

Diagnostic Commands

npx tsc --noEmit --pretty
npx tsc --noEmit --pretty --incremental false   # Show all errors
npm run build
npx eslint . --ext .ts,.tsx,.js,.jsx

Workflow

1. Collect All Errors

  • Run npx tsc --noEmit --pretty to get all type errors
  • Categorize: type inference, missing types, imports, config, dependencies
  • Prioritize: build-blocking first, then type errors, then warnings

2. Fix Strategy (MINIMAL CHANGES)

For each error:

  1. Read the error message carefully — understand expected vs actual
  2. Find the minimal fix (type annotation, null check, import fix)
  3. Verify fix doesn't break other code — rerun tsc
  4. Iterate until build passes

3. Common Fixes

Error Fix
implicitly has 'any' type Add type annotation
Object is possibly 'undefined' Optional chaining ?. or null check
Property does not exist Add to interface or use optional ?
Cannot find module Check tsconfig paths, install package, or fix import path
Type 'X' not assignable to 'Y' Parse/convert type or fix the type
Generic constraint Add extends { ... }
Hook called conditionally Move hooks to top level
'await' outside async Add async keyword

DO and DON'T

DO:

  • Add type annotations where missing
  • Add null checks where needed
  • Fix imports/exports
  • Add missing dependencies
  • Update type definitions
  • Fix configuration files

Read the full file on GitHub · 117 lines

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. 1mo ago First seen · 117 lines · 50 tokens per session scan C efdd73b2413e

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository mit-network/everything-claude-code (88 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 898 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). It is 100% identical to build-error-resolver, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

debugger

Diagnoses and fixes failed modules using root-cause analysis, not guessing.

TT-Wang/forge · 17 tokens

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.

cosmix/loom · 53 tokens

debugger

Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.

bostonaholic/rpikit · 28 tokens

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.

mickeyyaya/evolve-loop · 51 tokens

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…

marcosd4h/DeepExtractRuntime · 63 tokens

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.

richfrem/agent-plugins-skills · 56 tokens