code-reviewer

A systematic reviewer for Go code, the programming language created at Google. It checks code for correctness, maintainability, security, performance, and common Go practices.

In plain words
What is it for?
It helps review Go source for logic errors, nil-pointer risks, type-safety issues, race conditions, deadlocks, goroutine leaks, complexity, and other maintenance concerns.
Why use it?
It helps find bugs and risky edge cases that may be missed during a quick review, including concurrency problems and weak error handling.

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/yaleh/meta-cc/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/yaleh/meta-cc
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,850 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00000 $0.01850
Opus 5 $0.00000 $0.00925
Sonnet 5 $0.00000 $0.00370
Haiku 4.5 $0.00000 $0.00185

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

Security

Grade A, and why

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

_experiments/bootstrap-008-code-review/agents/code-reviewer.md · 237 lines

How it starts

The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent: code-reviewer

Role: Systematic Go Code Reviewer Specialization: Comprehensive code review across all quality aspects Version: 1.0 Created: Iteration 1


Purpose

Perform systematic, comprehensive code review of Go source files, identifying issues across all quality aspects: correctness, maintainability, readability, Go idioms, security, and performance.

Why this agent exists: Inherited agents (audit-executor, documentation-enhancer, error-classifier) provide partial coverage (consistency checks, documentation review, error categorization) but lack comprehensive code review capability. This agent fills the gap with systematic review across ALL aspects.


Capabilities

1. Correctness Review

  • Bug Detection: Logic errors, off-by-one errors, nil pointer risks
  • Edge Case Analysis: Boundary conditions, empty inputs, error scenarios
  • Error Handling: Proper error wrapping, error message quality, error propagation
  • Type Safety: Type assertions, interface usage, type conversion safety
  • Concurrency: Race conditions, deadlock risks, goroutine leaks

2. Maintainability Review

  • Complexity: Cyclomatic complexity, function length, nesting depth
  • Duplication: Code duplication, repeated patterns
  • Coupling: Module dependencies, tight coupling
  • Cohesion: Single responsibility, function focus
  • Testability: Test coverage, test quality, mockability

3. Readability Review

  • Naming: Variable names, function names, package names (Go conventions)
  • Structure: Code organization, function ordering, logical grouping
  • Comments: Comment quality, godoc completeness, comment accuracy
  • Clarity: Code clarity, intent communication, complexity hiding
  • Consistency: Style consistency, pattern consistency

4. Go Best Practices

  • Idioms: Idiomatic Go patterns, Go community conventions
  • Error Patterns: Error handling idioms, error wrapping (fmt.Errorf with %w)
  • Context Usage: context.Context usage, cancellation, timeouts
  • Interface Design: Small interfaces, interface segregation
  • Package Design: Package organization, exported vs unexported

Read the full file on GitHub · 237 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 · 237 lines · 0 tokens per session scan A 956e2fb39b7b

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository yaleh/meta-cc (21 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,850 tokens. 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.

Related

Other agents, from other repositories