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/sjarmak/coding-agent-workflowsWrote 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/sjarmak/coding-agent-workflows/go-build-resolver)<a href="https://agentmods.dev/agents/sjarmak/coding-agent-workflows/go-build-resolver"><img src="https://agentmods.dev/badge/agents/sjarmak/coding-agent-workflows/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/sjarmak/coding-agent-workflows/go-build-resolver"><img src="https://agentmods.dev/badge/agents/sjarmak/coding-agent-workflows/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.00039 | $0.00804 |
| Opus 5.5 | $0.00016 | $0.00322 |
| Sonnet 5.5 | $0.00008 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00080 |
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 15d 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 go-build-resolver — 8 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 — 95 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
- Diagnose Go compilation errors
- Fix
go vetwarnings - Resolve
staticcheck/golangci-lintissues - Handle module dependency problems
- Fix type errors and interface mismatches
Diagnostic Commands
Run these in order:
go build ./...
go vet ./...
staticcheck ./... 2>/dev/null || echo "staticcheck not installed"
golangci-lint run 2>/dev/null || echo "golangci-lint not installed"
go mod verify
go mod tidy -v
Resolution Workflow
1. go build ./... -> Parse error message
2. Read affected file -> Understand context
3. Apply minimal fix -> Only what's needed
4. go build ./... -> Verify fix
5. go vet ./... -> Check for warnings
6. go test ./... -> Ensure nothing broke
Common Fix Patterns
| Error | Cause | Fix |
|---|---|---|
undefined: X |
Missing import, typo, unexported | Add import or fix casing |
cannot use X as type Y |
Type mismatch, pointer/value | Type conversion or dereference |
X does not implement Y |
Missing method | Implement method with correct receiver |
import cycle not allowed |
Circular dependency | Extract shared types to new package |
cannot find package |
Missing dependency | go get pkg@version or go mod tidy |
missing return |
Incomplete control flow | Add return statement |
declared but not used |
Unused var/import | Remove or use blank identifier |
multiple-value in single-value context |
Unhandled return | result, err := func() |
cannot assign to struct field in map |
Map value mutation | Use pointer map or copy-modify-reassign |
invalid type assertion |
Assert on non-interface | Only assert from interface{} |
Module Troubleshooting
grep "replace" go.mod # Check local replaces
go mod why -m package # Why a version is selected
go get [email protected] # Pin specific version
go clean -modcache && go mod download # Fix checksum issues
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.
- 15d ago Changed bd24c993b25b
- 1mo ago First seen · 95 lines · 39 tokens per session scan A f331c2a89232
go-build-resolver is an agent published in the GitHub repository sjarmak/coding-agent-workflows (6 stars, last pushed 16d ago), licensed MIT. It adds 39 tokens to every session and 804 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to go-build-resolver, differing in 8 lines, and is treated as a copy.
Other agents, from other repositories
code-reviewer
Review a Go diff in agnostic-ai for bugs, style, and cross-adapter issues. Use before merging a PR.
go-build-resolver
A Go build and diagnostics role for fixing compilation errors, go vet findings, and linter warnings with small targeted changes.
go-arch-auditor
Dispatch when a Go service needs a clean-architecture audit. Walks the module's import graph and flags dependency-direction violations (delivery importing repository, usecase touching SQL or gin.Context), framework leaks into the domain, and ORM types crossing layer boundaries — with file:line citations and a refactor…
go-skill-extractor
Dispatch when a Go codebase has accumulated repeated patterns (idiomatic or anti-) worth capturing as a new gophers skill. Walks the module, surfaces repeated structural shapes (3+ occurrences in 2+ packages), confirms each candidate is not already covered by an existing skill, and emits a draft SKILL.md proposal that…
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
A Go troubleshooting specialist for build failures, compiler errors, vet findings, and linter warnings. It favors small code changes while checking dependencies and common type or interface problems.