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/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/go-build-resolver)<a href="https://agentmods.dev/agents/majiayu000/vibeguard/go-build-resolver"><img src="https://agentmods.dev/badge/agents/majiayu000/vibeguard/go-build-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/agents/majiayu000/vibeguard/go-build-resolver"><img src="https://agentmods.dev/badge/agents/majiayu000/vibeguard/go-build-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.00028 | $0.00297 |
| Opus 5 | $0.00014 | $0.00148 |
| Sonnet 5 | $0.00006 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
go-build-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 9d 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
Go Build Resolver Agent
Responsibilities
Quickly fix build/compile errors for Go projects.
Common error types
Compilation error
- Type mismatch → Fix type declaration
- Unused imports/variables → Remove (Go mandatory)
- Missing method implementation → Complete interface method
Module error
go.suminconsistent →go mod tidy- version conflicts → align versions in
go.mod - replace command issue → check local path
CGO Error
- Missing C library → prompt to install system dependencies
- Header file path → check
CGO_CFLAGS/CGO_LDFLAGS
Workflow
- Run
go build ./...to catch errors - Parsing errors, grouped by files
- Start repairing from the root cause (one repair may solve multiple errors)
- Re-verify
go buildafter each repair - Finally run
go vet ./...+go test ./...
VibeGuard Constraints
- Do not use
//nolintto bypass the problem - Solve problems that the standard library can solve without introducing new dependencies (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.
- 9d ago First seen · 43 lines · 28 tokens per session scan A 55dc34e7bc40
go-build-resolver is an agent published in the GitHub repository majiayu000/vibeguard (41 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 297 once invoked, about $0.0001 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
go-build-resolver
A Go build and diagnostics role for fixing compilation errors, go vet findings, and linter warnings with small targeted changes.
audit-bots
Audit Telegram bot code for goroutine safety, rate limits, callback integrity, and production readiness.
go-build-resolver
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.
go-build-resolver
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
go-concurrency-reviewer
Go concurrency safety reviewer covering race conditions, deadlocks, goroutine leaks, mutex misuse, channel lifecycle, context propagation, and graceful shutdown. Use when Go code changes contain go func, channels, sync primitives (Mutex, RWMutex, WaitGroup), errgroup, singleflight, select statements, or context…