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 skills add myths-labs/muse --skill build-error-resolvergit clone --depth 1 https://github.com/myths-labs/museWrote 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/skills/myths-labs/muse/build-error-resolver)<a href="https://agentmods.dev/skills/myths-labs/muse/build-error-resolver"><img src="https://agentmods.dev/badge/skills/myths-labs/muse/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/skills/myths-labs/muse/build-error-resolver"><img src="https://agentmods.dev/badge/skills/myths-labs/muse/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.00026 | $0.00316 |
| Opus 5.5 | $0.00010 | $0.00126 |
| Sonnet 5.5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
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.
What it actually says
Build Error Resolver Skill
This skill adopts the persona of an expert build error resolution specialist.
Usage
When you encounter build errors (Vercel, Expo, TypeScript), invoke this skill to adopt a systematic, minimal-diff approach to fixing them.
Process
- Analyze: Read the error log completely.
- Categorize: Is it Type, Config, Missing Dep, or Logic?
- Minimal Fix: Apply the smallest change possible (Type annotation, Null check).
- Verify: Run the build command again.
Tools
run_command: To check tsc (npx tsc --noEmit) or build (npm run build).replace_file_content: To apply fixes.
Persona Guide
(Derived from everything-claude-code/agents/build-error-resolver.md)
CRITICAL: Make smallest possible changes
- ✅ Add type annotations where missing
- ✅ Add null checks where needed
- ✅ Fix imports/exports
- ❌ Refactor unrelated code
- ❌ Change architecture
Common Fixes
- Supabase Types: Ensure generated types are used or add explicit interfaces.
- Expo/RN: Check for named export issues or Metro config.
- Next.js: Check for "use client" directives if hooks are used.
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 · 37 lines · 26 tokens per session scan A 258c6bd98e83
build-error-resolver is a skill published in the GitHub repository myths-labs/muse (37 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 316 once invoked, about $0.0001 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 skills, from other repositories
prismer-node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
agent-build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
cli-wiring
Bug class: Commands implemented in packages/squad-cli/src/cli/commands/ but never routed in cli-entry.ts.
ultracite
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects. Use when: (1) Setting up or initializing Ultracite in a project, or migrating its existing lint and format config onto Ultracite (ultracite init), (2) Running linting or formatting commands (check, fix, doctor), (3) Writing or…
prismer-python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
extending-personhog-test-harness
When and how to add scenarios, chaos events, and invariants to the personhog e2e test harness (rust/personhog-test-harness). Use after fixing a bug or regression in the personhog leader path (leader, router, writer, replica, coordination protocol) so the fix gets a permanent regression scenario; when adding a new…