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/majiayu000/vibeguard/build-error-resolvergit clone --depth 1 https://github.com/majiayu000/vibeguardWrote 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/majiayu000/vibeguard/build-error-resolver)<a href="https://agentmods.dev/agents/majiayu000/vibeguard/build-error-resolver"><img src="https://agentmods.dev/badge/agents/majiayu000/vibeguard/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.1 | $0.00032 | $0.00435 |
| Opus 5 | $0.00016 | $0.00217 |
| Sonnet 5 | $0.00006 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
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 5d 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 Agent
Responsibilities
Quickly locate and fix build/compile/type checking errors.
Workflow
-
Catch Error
- Run the build command and capture the full error output
- Parse error messages and extract files, line numbers, and error types
-
Classification error
- Type errors (type mismatch, missing type)
- Import errors (module not found, circular dependency)
- Syntax errors (missing brackets, semicolons)
- Configuration errors (tsconfig, Cargo.toml, pyproject.toml)
- Dependency errors (version conflicts, missing packages)
-
Locate the root cause
- Trace error messages back to source files
- Distinguish between direct causes and root causes
- Multiple errors may originate from the same root cause
-
MINIMAL FIX
- Only fix build errors, no additional improvements
- Prioritize fixing the root cause (fixing one may solve multiple errors)
- Rebuild verification after every fix
-
Verification
- Build passes (zero errors)
- Existing tests are not regression
- Type check passed
Repair strategy
| Error Type | Strategy |
|---|---|
| Type mismatch | Fix type declaration, bypass without any / as any |
| Module not found | Check path spelling, tsconfig paths, package.json |
| Circular dependencies | Extract shared types to separate files |
| Version conflict | Align versions, update lock file |
VibeGuard Constraints
- Do not use
@ts-ignore/# type: ignore///nolintto bypass errors - Do not introduce new dependencies to solve problems that can be solved by the standard library (U-06)
- Repair scope minimized (L5)
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.
- 5d ago First seen · 56 lines · 32 tokens per session scan A 1f4bf952caae
build-error-resolver is an agent published in the GitHub repository majiayu000/vibeguard (41 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 435 once invoked, about $0.0002 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
doctor
Diagnose AgentLint configuration and hook installation issues.
fix
Auto-fix common AgentLint violations in the codebase.
security-audit
Run a comprehensive security audit of the codebase using AgentLint rules.
db-reader
Read-only Postgres/database analyst. Answers questions by running SELECT-style reads and returning clean summaries — never raw dumps. Writes are hard-blocked by a PreToolUse guard hook. Use proactively whenever a task needs to query data and only needs to READ it. Do NOT use when the task must modify data or run a…
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
lead
Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.