ECC is a toolkit that organizes and improves how coding agents work through skills, memory, security checks, research practices, and related extensions. It is for developers using agents such as Claude Code, Codex, OpenCode, and Cursor.
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/affaan-m/ECCWrote 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/affaan-m/ecc/go-build-resolver)<a href="https://agentmods.dev/agents/affaan-m/ecc/go-build-resolver"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/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/affaan-m/ecc/go-build-resolver"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/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.00783 |
| Opus 5.5 | $0.00016 | $0.00313 |
| Sonnet 5.5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
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 1mo 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- go-build-resolver — 100% identical, 0 lines differ
- go-build-resolver — 100% identical, 0 lines differ
- go-build-resolver — 100% identical, 0 lines differ
- go-build-resolver — 100% identical, 0 lines differ
- go-build-resolver — 100% identical, 0 lines differ
- go-build-resolver — 100% identical, 0 lines differ
- go-build-resolver — 92% identical, 13 lines differ
- go-build-resolver — 91% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 97 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.
- 1mo ago First seen · 97 lines · 39 tokens per session scan A e85d2baa1e6d
go-build-resolver is an agent published in the GitHub repository affaan-m/ECC (285,716 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 783 once invoked, about $0.0002 per session on Opus 5.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.
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-reviewer
A specialist reviewer for Go code, the programming language created at Google. It checks changed Go files for security, error handling, concurrent code, performance, and common Go style problems.
audit-bots
Audit Telegram bot code for goroutine safety, rate limits, callback integrity, and production readiness.
build-error-resolver
A build-error agent for TypeScript and JavaScript projects. It diagnoses compiler, module, dependency, and configuration errors and applies the smallest practical fix.
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.