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/commands/affaan-m/ecc/go-review)<a href="https://agentmods.dev/commands/affaan-m/ecc/go-review"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/go-review/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/commands/affaan-m/ecc/go-review"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/go-review.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.00007 | $0.00442 |
| Opus 5.5 | $0.00003 | $0.00177 |
| Sonnet 5.5 | $0.00001 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
go-review 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-review — 100% identical, 0 lines differ
- go-review — 100% identical, 0 lines differ
- go-review — 100% identical, 0 lines differ
- go-review — 100% identical, 0 lines differ
- go-review — 100% identical, 0 lines differ
- go-review — 100% identical, 0 lines differ
- go-review — 98% identical, 2 lines differ
- go-review — 97% identical, 2 lines differ
What it actually says
Go Review Command
Review Go code for idiomatic patterns and best practices: $ARGUMENTS
Your Task
- Analyze Go code for idioms and patterns
- Check concurrency - goroutines, channels, mutexes
- Review error handling - proper error wrapping
- Verify performance - allocations, bottlenecks
Review Checklist
Idiomatic Go
- Package naming (lowercase, no underscores)
- Variable naming (camelCase, short)
- Interface naming (ends with -er)
- Error naming (starts with Err)
Error Handling
- Errors are checked, not ignored
- Errors wrapped with context (
fmt.Errorf("...: %w", err)) - Sentinel errors used appropriately
- Custom error types when needed
Concurrency
- Goroutines properly managed
- Channels buffered appropriately
- No data races (use
-raceflag) - Context passed for cancellation
- WaitGroups used correctly
Performance
- Avoid unnecessary allocations
- Use
sync.Poolfor frequent allocations - Prefer value receivers for small structs
- Buffer I/O operations
Code Organization
- Small, focused packages
- Clear dependency direction
- Internal packages for private code
- Godoc comments on exports
Report Format
Idiomatic Issues
- [file:line] Issue description Suggestion: How to fix
Error Handling Issues
- [file:line] Issue description Suggestion: How to fix
Concurrency Issues
- [file:line] Issue description Suggestion: How to fix
Performance Issues
- [file:line] Issue description Suggestion: How to fix
TIP: Run go vet and staticcheck for additional automated checks.
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 · 72 lines · 7 tokens per session scan A f082baa55817
go-review is a command published in the GitHub repository affaan-m/ECC (289,862 stars, last pushed yesterday), licensed MIT. It adds 7 tokens to every session and 442 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
go-review
Comprehensive Go code review for idiomatic patterns, concurrency safety, error handling, and security. Invokes the go-reviewer agent.
go-review
Go code review for idiomatic patterns.
caveman-review
Caveman-style code review — one-line findings with severity.
code-review
Code review a pull request.
skill-go-gin-api
Padrões DARE para APIs REST em Go + Gin (ou stdlib net/http) + sqlc + PostgreSQL. Handlers, services, repositories, middleware, validador, JWT, rate limit, swag OpenAPI.
go-test
Enforce TDD workflow for Go. Write table-driven tests first, then implement. Verify 80%+ coverage with go test -cover.