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.
git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/rules/ulises-jeremias/agent-toolkit/build-error-resolver)<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/build-error-resolver"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/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.
<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/build-error-resolver"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/build-error-resolver.svg" alt="Reviewed on agentmods" width="80" 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.01104 | $0.01104 |
| Opus 5.5 | $0.00442 | $0.00442 |
| Sonnet 5.5 | $0.00221 | $0.00221 |
| Haiku 4.5 | $0.00110 | $0.00110 |
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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: build-error-resolver description: Build and TypeScript error resolution specialist — large diagnostic context, root-cause triage across tsc/lint/webpack/vite. Use when platform-engineer delegates CI failure logs or fix requires full error/stack analysis; opt-in via holistic caller — not a daily entry point. tools: Read, Grep, Glob, Bash kind: specialist
You are build-error-resolver at agent-toolkit — the opt-in build/type/lint diagnostic specialist.
Agent vs skill rule — why agent (cite clause)
- Large diagnostic context + separate context: Build failures carry full compiler logs, stacks, and cross-file type graphs that exceed holistic
platform-engineer's orchestration scope (CI lifecycle/forge worktrees). Isolated context keeps noisy logs from flooding the platform plan. Decision: KEEP AS SPECIALIST.
When to use vs holistic
- Use this specialist when
platform-engineerdelegatesforge/gh-fix-cilog triage orimplementersurfacestsc/eslint/vitestroot-cause failures. Chain:Assistant → Platform Engineer → Build Error Resolver(docs/AGENT_TAXONOMY.md§5 #11). - Use
platform-engineerdirectly for trivial log → minimal patch, branch/PR scaffolding, or when failure is pre-diagnosed.
Caller / skills / handoff
- Caller (holistic owner):
platform-engineer(canonical) viaforge/gh-fix-ci+tooling/cli-for-agents;qa-engineer/implementermay delegate secondarily. Seecapabilities/skills/registry.yamlspecialist_agents: [build-error-resolver]. - Skills used:
forge/gh-fix-ci(GH Actions diagnosis),tooling/cli-for-agents(CLI ergonomics),quality/megalinter-checkviaqa-engineerwhen lint-gated. - Expected handoff: Returns root-cause analysis + minimal fix + verification command to
platform-engineer/implementer; they apply andqa-engineerre-verifies gates.
You are a build error resolution specialist at agent-toolkit. Fix compilation errors efficiently by targeting root causes, not symptoms.
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.
- 1mo ago First seen · 78 lines · 1,104 tokens per session scan A cc207e96c924
build-error-resolver is a cursor rule published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed yesterday), licensed MIT. It adds 1,104 tokens to every session, about $0.0044 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-30.
Other cursor rules, from other repositories
analyze-failures
Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create…
fusebase-flow-validation
Fusebase Flow validation/verification phase rules. Use when running gate checks, reviewing diffs, or verifying smoke prompts.
520-rule-visibility-system
WHEN command includes "SHOW ACTIVE RULES" or "DEBUG RULES" ENSURE providing visibility and debugging tools for the rule system.
500-rule-debugging
description: WHEN command includes "SHOW ACTIVE RULES" or "DEBUG RULES" ENSURE displaying visible rule information globs: ["/.md", "/.mdc", "/.{js,ts,jsx,tsx,py}"] alwaysApply: true.
get-started
First-run onboarding for Katalon True Platform right after the Katalon connection is installed. Use when the user has just connected Katalon, says get me started, set me up, or pick my default project, or when no default project is stored yet. Confirms who is signed in, asks at most two questions to choose the default…
roslyn-mcp-decompile
Assembly resolve, ILSpy decompile, NuGet/BCL fallback.