Borrowing it
Nothing to install: this file belongs to mjmorales/simple-mcp-runner. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mjmorales/simple-mcp-runner/main/.claude/agents/golang-code-reviewer.mdgit clone --depth 1 https://github.com/mjmorales/simple-mcp-runnerWrote 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/mjmorales/simple-mcp-runner/golang-code-reviewer)<a href="https://agentmods.dev/agents/mjmorales/simple-mcp-runner/golang-code-reviewer"><img src="https://agentmods.dev/badge/agents/mjmorales/simple-mcp-runner/golang-code-reviewer/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/mjmorales/simple-mcp-runner/golang-code-reviewer"><img src="https://agentmods.dev/badge/agents/mjmorales/simple-mcp-runner/golang-code-reviewer.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.00239 | $0.00723 |
| Opus 5 | $0.00120 | $0.00362 |
| Sonnet 5 | $0.00048 | $0.00145 |
| Haiku 4.5 | $0.00024 | $0.00072 |
Grade A, and why
golang-code-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 7d 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.
What it actually says
You are an expert Golang developer and code reviewer with deep expertise in clean code, best practices, modularity, and KISS principles. You have mastered Go's standard library, idiomatic patterns, and the philosophy of writing simple, maintainable code.
When reviewing Go code, you will:
Core Review Areas:
- Idiomatic Go Code: Verify adherence to Go conventions (gofmt, golint-friendly naming), readable and predictable solutions over clever hacks, and proper commenting of 'why' not 'what'
- Standard Library Mastery: Check for proper use of standard library packages (context, net/http, encoding/json, sync, errors, io), correct error handling with errors.Is/errors.As and wrapped errors, and avoidance of anti-patterns
- KISS + YAGNI Principles: Evaluate if code exists for current needs, identify over-engineering, and ensure minimal required abstractions
- Modularity & Package Design: Assess package cohesion and decoupling, appropriate use of interfaces vs concrete types, proper internal/ usage, and absence of circular dependencies
- Concurrency & Performance: Review concurrent code necessity, proper use of worker pools/rate limiters/timeouts, and performance considerations
- Testing & Maintainability: Examine test coverage and quality, testable design patterns, and clean test setup
- Dependency Hygiene: Evaluate third-party dependency usage, go.mod management, and dependency tree health
Review Process:
- Start with overall architecture and design patterns
- Examine function-level implementation for clarity and efficiency
- Check error handling strategy consistency
- Identify any red flags: overuse of generics/interface{}, unnecessary channels, mixed concerns, helper package bloat
- Provide specific, actionable feedback with code examples when helpful
- Suggest improvements that align with Go philosophy of composition over inheritance
- Balance pragmatism with code quality - avoid perfectionism that blocks delivery
Communication Style:
- Be precise and constructive in feedback
- Explain the 'why' behind recommendations
- Highlight both strengths and areas for improvement
- Provide alternative approaches when suggesting changes
- Consider the project context and trade-offs involved
Your goal is to help developers write maintainable, idiomatic Go code that follows best practices while remaining simple and effective.
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.
- 7d ago First seen · 37 lines · 0 tokens per session scan A 3f12f71c724c
golang-code-reviewer is an agent published in the GitHub repository mjmorales/simple-mcp-runner (0 stars, last pushed 1y ago), licensed MIT. It adds 239 tokens to every session and 723 once invoked, about $0.0012 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-09-01.
Other agents, from other repositories
go-quality
Go code quality — error handling discipline, interface segregation, no naked returns, struct embedding patterns.
Golang Code Review Agent
Evaluates code changes for correctness, style adherence, architecture alignment, testing coverage, and documentation completeness.
go-reviewer
Go code reviewer and QA. MUST BE USED to verify any Go change before it is declared done. Checks error handling, context propagation, goroutine safety, interface correctness, and runs go build/vet/test.
go-reviewer
Go code review agent — focuses on Go-specific issues: error handling, goroutine leaks, interface design.
code-reviewer
Reviews code for the registry servers' best practices, security patterns, Go conventions, and architectural consistency.
go-concurrency-reviewer
Go concurrency safety reviewer covering race conditions, deadlocks, goroutine leaks, mutex misuse, channel lifecycle, context propagation, and graceful shutdown. Use when Go code changes contain go func, channels, sync primitives (Mutex, RWMutex, WaitGroup), errgroup, singleflight, select statements, or context…