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/multiplex-ai/muggle-ai-teamsWrote 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/commands/multiplex-ai/muggle-ai-teams/build-fix)<a href="https://agentmods.dev/commands/multiplex-ai/muggle-ai-teams/build-fix"><img src="https://agentmods.dev/badge/commands/multiplex-ai/muggle-ai-teams/build-fix.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.1 | $0.00000 | $0.00561 |
| Opus 5 | $0.00000 | $0.00280 |
| Sonnet 5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
build-fix 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 8d 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.
This is a copy
91% identical to build-fix — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build and Fix
Incrementally fix build and type errors with minimal, safe changes.
Step 1: Detect Build System
Identify the project's build tool and run the build:
| Indicator | Build Command |
|---|---|
package.json with build script |
npm run build or pnpm build |
tsconfig.json (TypeScript only) |
npx tsc --noEmit |
Cargo.toml |
cargo build 2>&1 |
pom.xml |
mvn compile |
build.gradle |
./gradlew compileJava |
go.mod |
go build ./... |
pyproject.toml |
python -m py_compile or mypy . |
Step 2: Parse and Group Errors
- Run the build command and capture stderr
- Group errors by file path
- Sort by dependency order (fix imports/types before logic errors)
- Count total errors for progress tracking
Step 3: Fix Loop (One Error at a Time)
For each error:
- Read the file — Use Read tool to see error context (10 lines around the error)
- Diagnose — Identify root cause (missing import, wrong type, syntax error)
- Fix minimally — Use Edit tool for the smallest change that resolves the error
- Re-run build — Verify the error is gone and no new errors introduced
- Move to next — Continue with remaining errors
Step 4: Guardrails
Stop and ask the user if:
- A fix introduces more errors than it resolves
- The same error persists after 3 attempts (likely a deeper issue)
- The fix requires architectural changes (not just a build fix)
- Build errors stem from missing dependencies (need
npm install,cargo add, etc.)
Step 5: Summary
Show results:
- Errors fixed (with file paths)
- Errors remaining (if any)
- New errors introduced (should be zero)
- Suggested next steps for unresolved issues
Recovery Strategies
| Situation | Action |
|---|---|
| Missing module/import | Check if package is installed; suggest install command |
| Type mismatch | Read both type definitions; fix the narrower type |
| Circular dependency | Identify cycle with import graph; suggest extraction |
| Version conflict | Check package.json / Cargo.toml for version constraints |
| Build tool misconfiguration | Read config file; compare with working defaults |
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.
- 8d ago First seen · 63 lines · 0 tokens per session scan A 5088ccbffd1f
build-fix is a command published in the GitHub repository multiplex-ai/muggle-ai-teams (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 561 tokens. A static security scan graded it A with 0 findings. It is 91% identical to build-fix, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
diagnose-runtime
Quickly diagnose runtime performance issues in web applications including freezes, hangs, memory leaks, and slow performance.
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
investigate
Systematic root-cause debugging — find the cause before writing any fix.
time-travel
Debugger de razonamiento que muestra por qué el framework eligió cada modelo, skill y decisión. Usa cuando el usuario dice "time travel", "por qué eligió", "reasoning debug", "decision audit", "why this model", "razonamiento", "debug reasoning", "explain decision", "modelo elegido". Permite ajustar skills…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…