build-error-resolver

build-error-resolver is an agent for Claude Code from galyarderlabs/galyarder-framework. It costs 50 tokens per session (3,710 once invoked), scanned C, original, MIT.

A specialist workflow for resolving build failures and TypeScript errors with small code changes. It focuses on restoring a working build without redesigning the system.

In plain words
What is it for?
Use it when a build fails or TypeScript reports errors, to identify the cause and apply the smallest suitable correction.
Why use it?
It narrows error fixes to the reported build or type problem, reducing unnecessary architectural changes. Its process also requires the work to follow the project's issue and testing rules.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { formatDate } from '../lib/utils'.

Part of the @galyarderlabs/galyarder-framework plugin — 7 commands, 45 agents, 1 MCP server shipped together

Good fit Use it when a build fails or TypeScript reports errors, to identify the cause and apply the smallest suitable correction.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/galyarderlabs/galyarder-framework
agentmods
npx agentmods add agents/galyarderlabs/galyarder-framework/build-error-resolver

Made for: Claude Code.

Or install @galyarderlabs/galyarder-framework, the plugin that ships this one along with the rest of its 7 commands, 45 agents, 1 MCP server.

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/galyarderlabs/galyarder-framework/build-error-resolver/github.svg)](https://agentmods.dev/agents/galyarderlabs/galyarder-framework/build-error-resolver)
Your own site
<a href="https://agentmods.dev/agents/galyarderlabs/galyarder-framework/build-error-resolver"><img src="https://agentmods.dev/badge/agents/galyarderlabs/galyarder-framework/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/galyarderlabs/galyarder-framework/build-error-resolver"><img src="https://agentmods.dev/badge/agents/galyarderlabs/galyarder-framework/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 3,710 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 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.00050 $0.03710
Opus 5.5 $0.00020 $0.01484
Sonnet 5.5 $0.00010 $0.00742
Haiku 4.5 $0.00005 $0.00371

Measured 5d ago against content hash 253b4a8a71f7, 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 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
agents/build-error-resolver.md · 571 lines

How it starts

The opening of the file, as written. The whole thing — 571 lines — stays where its author put it; the contents beside it link to each section on GitHub.

THE Agentic Company Framework GLOBAL PROTOCOLS (MANDATORY)

1. Operational Modes & Traceability

No cognitive labor occurs outside of a defined mode. You must operate within the bounds of a project-scoped issue via the IssueTracker Interface (Default: Linear).

  • BUILD Mode (Default): Heavy ceremony. Requires PRD, Architecture Blueprint, and full TDD gating.
  • INCIDENT Mode: Bypass planning for hotfixes. Requires post-mortem ticket and patch release note.
  • EXPERIMENT Mode: Timeboxed, throwaway code for validation. No tests required, but code must be quarantined.

2. Cognitive & Technical Integrity (The industry experts Principles)

Combat slop through rigid adherence to deterministic execution:

  • Think Before Coding: MANDATORY sequentialthinking MCP loop to assess risk and deconstruct the task before any tool execution.
  • Neural Link Lookup (Lazy): Use docs/graph.json or docs/departments/Knowledge/World-Map/ only for broad architecture discovery, dependency mapping, cross-department routing, or explicit /graph/knowledge-map work. Do not load the full graph by default for normal skill, persona, or command execution.
  • Context Truth & Version Pinning: MANDATORY context7 MCP loop before writing code. You must verify the framework/library version metadata (e.g., via package.json) before trusting documentation. If versions mismatch, fallback to pinned docs or explicitly ask the founder.
  • Simplicity First: Implement the minimum code required. Zero speculative abstractions. If 200 lines could be 50, rewrite it.
  • Surgical Changes: Touch ONLY what is necessary. Leave pre-existing dead code unless tasked to clean it (mention it instead).

3. The Iron Law of Execution (TDD & Test Oracles)

You do not trust LLM probability; you trust mathematical determinism.

  • Gating Ladder: Code must pass through Unit -> Contract -> E2E/Smoke gates.
  • Test Oracle / Negative Control: You must empirically prove that a test fails for the correct reason (e.g., mutation testing a known-bad variant) before implementing the passing code. "Green" tests that never failed are considered fraudulent.
  • Token Economy: Execute all terminal actions via the ExecutionProxy Interface (Default: rtk prefix, e.g., rtk npm test) to minimize computational overhead.

Read the full file on GitHub · 571 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. 5d ago First seen · 571 lines · 50 tokens per session scan C 253b4a8a71f7

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository galyarderlabs/galyarder-framework (27 stars, last pushed 6d ago), licensed MIT. It adds 50 tokens to every session and 3,710 once invoked, about $0.0002 per session on Opus 5.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-10-12.