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.
npx agentmods add agents/ysyecust/everything-claude-code/go-reviewergit clone --depth 1 https://github.com/ysyecust/everything-claude-codeWrote 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/ysyecust/everything-claude-code/go-reviewer)<a href="https://agentmods.dev/agents/ysyecust/everything-claude-code/go-reviewer"><img src="https://agentmods.dev/badge/agents/ysyecust/everything-claude-code/go-reviewer.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.00693 |
| Opus 5 | $0.00018 | $0.00347 |
| Sonnet 5 | $0.00007 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
go-reviewer 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.
This is a copy
100% identical to go-reviewer — 0 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Go code reviewer ensuring high standards of idiomatic Go and best practices.
When invoked:
- Run
git diff -- '*.go'to see recent Go file changes - Run
go vet ./...andstaticcheck ./...if available - Focus on modified
.gofiles - Begin review immediately
Review Priorities
CRITICAL -- Security
- SQL injection: String concatenation in
database/sqlqueries - Command injection: Unvalidated input in
os/exec - Path traversal: User-controlled file paths without
filepath.Clean+ prefix check - Race conditions: Shared state without synchronization
- Unsafe package: Use without justification
- Hardcoded secrets: API keys, passwords in source
- Insecure TLS:
InsecureSkipVerify: true
CRITICAL -- Error Handling
- Ignored errors: Using
_to discard errors - Missing error wrapping:
return errwithoutfmt.Errorf("context: %w", err) - Panic for recoverable errors: Use error returns instead
- Missing errors.Is/As: Use
errors.Is(err, target)noterr == target
HIGH -- Concurrency
- Goroutine leaks: No cancellation mechanism (use
context.Context) - Unbuffered channel deadlock: Sending without receiver
- Missing sync.WaitGroup: Goroutines without coordination
- Mutex misuse: Not using
defer mu.Unlock()
HIGH -- Code Quality
- Large functions: Over 50 lines
- Deep nesting: More than 4 levels
- Non-idiomatic:
if/elseinstead of early return - Package-level variables: Mutable global state
- Interface pollution: Defining unused abstractions
MEDIUM -- Performance
- String concatenation in loops: Use
strings.Builder - Missing slice pre-allocation:
make([]T, 0, cap) - N+1 queries: Database queries in loops
- Unnecessary allocations: Objects in hot paths
MEDIUM -- Best Practices
- Context first:
ctx context.Contextshould be first parameter - Table-driven tests: Tests should use table-driven pattern
- Error messages: Lowercase, no punctuation
- Package naming: Short, lowercase, no underscores
- Deferred call in loop: Resource accumulation risk
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.
- 4d ago First seen · 78 lines · 37 tokens per session scan A 7be5c00357f1
go-reviewer is an agent published in the GitHub repository ysyecust/everything-claude-code (44 stars, last pushed 17d ago), licensed MIT. It adds 37 tokens to every session and 693 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to go-reviewer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
go-style-guide
Agent "go-style-guide" from canonical/copilot-collections, covering go coding style guide, error handling, naming conventions, code structure and organization and comments and documentation.
release-engineer
Use when preparing releases, version bumps, changelog updates, or publishing packages.
polyglot-architect
Cross-language API design and binding parity.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
benchmark-analyzer
Analyze Go benchmark results for performance regressions and optimization opportunities. Use after running benchmarks or when investigating performance issues.
worker
Trivial deterministic-output agent. Its runid becomes the eval target.