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.
npx agentmods add agents/ulises-jeremias/agent-toolkit/build-error-resolvergit 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/agents/ulises-jeremias/agent-toolkit/build-error-resolver)<a href="https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/build-error-resolver"><img src="https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/build-error-resolver.svg" alt="Measured on agentmods" 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 | $0.00062 | $0.01090 |
| Opus 5 | $0.00031 | $0.00545 |
| Sonnet 5 | $0.00012 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
When invoked
- Read the full error message including stack trace
- Locate the source files mentioned in the error
- Understand the context before changing anything
- Apply the minimal fix that resolves the root cause
Common error types
- TypeScript: missing types, incorrect generics, incompatible assignments
- Import/export: missing modules, wrong paths, circular dependencies
- ESLint/Prettier: formatting, unused vars, rule violations
- Build config: webpack/vite/tsc configuration issues
- Dependency conflicts: incompatible package versions
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.
- 4d ago First seen · 73 lines · 62 tokens per session scan A bab38c5d08ae
build-error-resolver is an agent published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 1,090 once invoked, about $0.0003 per session on Opus 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 agents, from other repositories
accessibility-reviewer
Audits SwiftUI and UIKit code for VoiceOver, Dynamic Type, contrast, tap targets, and motion/transparency settings. Read-only — reports findings with file:line and the specific fix. Use before shipping a screen or when an accessibility issue is reported.
foundation-models
Specialist for Apple's Foundation Models framework and Apple Intelligence — on-device and Private Cloud Compute language models, @Generable structured output, tool calling, Dynamic Profiles, and multimodal prompts. Use when building, reviewing, or debugging any on-device LLM feature. Enforces availability gating and…
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
security-auditor
Security specialist for CrawlForge MCP Server. Audits code for vulnerabilities, ensures secure practices, validates input sanitization. Use PROACTIVELY before deployments and after major changes.
debug-integracao
Especialista em diagnóstico de problemas em integrações com a API da Tray. Utilize quando encontrar erros de autenticação, tokens expirados, limites de requisições excedidos, respostas inesperadas da API ou problemas de validação de dados.
threnody-low
Threnody low-tier host subagent for boilerplate and small edits.