go-reviewer

A Go code-review assistant for checking changed Go files for common security, error-handling, concurrency, and performance problems.

In plain words
What is it for?
Use it after changing Go code to inspect the diff and run checks such as go vet and staticcheck when available.
Why use it?
It helps catch bugs and unsafe patterns that are easy to miss during a normal review, including race conditions, ignored errors, and hardcoded secrets.

Agent

Install

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.

agentmods
npx agentmods add agents/arogyareddy/https-github.com-affaan-m-everything-claude-code1/go-reviewer
Clone the repo
git clone --depth 1 https://github.com/ArogyaReddy/https-github.com-affaan-m-everything-claude-code1
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 693 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 7be5c00357f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

Origin

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.

.kiro/agents/go-reviewer.md · 78 lines

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:

  1. Run git diff -- '*.go' to see recent Go file changes
  2. Run go vet ./... and staticcheck ./... if available
  3. Focus on modified .go files
  4. Begin review immediately

Review Priorities

CRITICAL -- Security

  • SQL injection: String concatenation in database/sql queries
  • 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 err without fmt.Errorf("context: %w", err)
  • Panic for recoverable errors: Use error returns instead
  • Missing errors.Is/As: Use errors.Is(err, target) not err == 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/else instead 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.Context should 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

Read the full file on GitHub · 78 lines

Changes

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.

  1. 2d ago First seen · 78 lines · 37 tokens per session scan A 7be5c00357f1

Subscribe to this mod's changes

go-reviewer is an agent published in the GitHub repository ArogyaReddy/https-github.com-affaan-m-everything-claude-code1 (2 stars, last pushed 4mo 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.