build-error-resolver

A helper for fixing TypeScript and frontend build failures, including type errors, unresolved imports, and configuration problems.

In plain words
What is it for?
Use it when `tsc --noEmit` or `npm run build` fails, or when problems involve `tsconfig`, webpack, or Next.js configuration.
Why use it?
It helps remove build blockers without making broad architectural changes or creating large diffs.

Agent

Install

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.

agentmods
npx agentmods add agents/venthezone/pi-dots/build-error-resolver
Clone the repo
git clone --depth 1 https://github.com/VenTheZone/pi-dots
Per session 63 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,055 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin unknown 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 $0.00063 $0.01055
Opus 5 $0.00032 $0.00528
Sonnet 5 $0.00013 $0.00211
Haiku 4.5 $0.00006 $0.00105

Measured 2d ago against content hash 6cb2376e9471, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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
pi-agents/agents/build-error-resolver.md · 162 lines

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.

Read it on GitHub

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. 2d ago First seen · 162 lines · 63 tokens per session scan C 6cb2376e9471

Subscribe to this mod's changes

build-error-resolver is an agent published in the GitHub repository VenTheZone/pi-dots (43 stars, last pushed 25d ago), with no licence file. It adds 63 tokens to every session and 1,055 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-30.