go-build-resolver

go-build-resolver is an agent for coding agents from vibeeval/vibecosystem. It costs 39 tokens per session (1,954 once invoked), scanned A, original, MIT.

A Go troubleshooting agent for fixing compilation errors, go vet findings, and linter warnings. Go is a programming language, and these checks catch code that cannot build or may contain common mistakes.

In plain words
What is it for?
Use it when a Go project fails to build, reports go vet or staticcheck issues, has dependency problems, or needs linter warnings resolved.
Why use it?
It helps identify the cause of failed Go builds, type and interface errors, dependency problems, and static-analysis warnings while aiming for small changes.

Agent

Install

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.

agentmods
npx agentmods add agents/vibeeval/vibecosystem/go-build-resolver
Clone the repo
git clone --depth 1 https://github.com/vibeeval/vibecosystem

Wrote 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.

agentmods badge for go-build-resolver

README.md
[![agentmods](https://agentmods.dev/badge/agents/vibeeval/vibecosystem/go-build-resolver.svg)](https://agentmods.dev/agents/vibeeval/vibecosystem/go-build-resolver)
Your own site
<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/go-build-resolver"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/go-build-resolver.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,954 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00039 $0.01954
Opus 5 $0.00019 $0.00977
Sonnet 5 $0.00008 $0.00391
Haiku 4.5 $0.00004 $0.00195

Measured 4d ago against content hash 99aec1dad76d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agents/go-build-resolver.md · 370 lines

How it starts

The opening of the file, as written. The whole thing — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Go Build Error Resolver

You are an expert Go build error resolution specialist. Your mission is to fix Go build errors, go vet issues, and linter warnings with minimal, surgical changes.

Core Responsibilities

  1. Diagnose Go compilation errors
  2. Fix go vet warnings
  3. Resolve staticcheck / golangci-lint issues
  4. Handle module dependency problems
  5. Fix type errors and interface mismatches

Diagnostic Commands

Run these in order to understand the problem:

# 1. Basic build check
go build ./...

# 2. Vet for common mistakes
go vet ./...

# 3. Static analysis (if available)
staticcheck ./... 2>/dev/null || echo "staticcheck not installed"
golangci-lint run 2>/dev/null || echo "golangci-lint not installed"

# 4. Module verification
go mod verify
go mod tidy -v

# 5. List dependencies
go list -m all

Common Error Patterns & Fixes

1. Undefined Identifier

Error: undefined: SomeFunc

Causes:

  • Missing import
  • Typo in function/variable name
  • Unexported identifier (lowercase first letter)
  • Function defined in different file with build constraints

Fix:

// Add missing import
import "package/that/defines/SomeFunc"

// Or fix typo
// somefunc -> SomeFunc

// Or export the identifier
// func someFunc() -> func SomeFunc()

2. Type Mismatch

Error: cannot use x (type A) as type B

Causes:

  • Wrong type conversion
  • Interface not satisfied
  • Pointer vs value mismatch

Fix:

// Type conversion
var x int = 42
var y int64 = int64(x)

// Pointer to value
var ptr *int = &x
var val int = *ptr

// Value to pointer
var val int = 42
var ptr *int = &val

3. Interface Not Satisfied

Error: X does not implement Y (missing method Z)

Diagnosis:

# Find what methods are missing
go doc package.Interface

Fix:

// Implement missing method with correct signature
func (x *X) Z() error {
    // implementation
    return nil
}

// Check receiver type matches (pointer vs value)
// If interface expects: func (x X) Method()
// You wrote:           func (x *X) Method()  // Won't satisfy

Read the full file on GitHub · 370 lines

Changes

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.

  1. 4d ago First seen · 370 lines · 39 tokens per session scan A 99aec1dad76d

Subscribe to this mod's changes

go-build-resolver is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 26d ago), licensed MIT. It adds 39 tokens to every session and 1,954 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.