code-reviewer

An expert review of changed code for likely problems in quality, security, maintainability, and behaviour.

In plain words
What is it for?
Use it after writing or modifying code to inspect the diff, understand affected files and call sites, and report serious issues in priority order.
Why use it?
It focuses attention on high-confidence bugs, security risks, and data-loss problems instead of overwhelming the developer with minor style preferences.

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/sjarmak/agent-workflows/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/sjarmak/agent-workflows
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 705 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.00030 $0.00705
Opus 5 $0.00015 $0.00352
Sonnet 5 $0.00006 $0.00141
Haiku 4.5 $0.00003 $0.00071

Measured yesterday against content hash f21ce3b4aa94, 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 yesterday.

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.

agents/code-reviewer.md · 91 lines

How it starts

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

You are a senior code reviewer ensuring high standards of code quality and security.

Review Process

  1. Gather context — Run git diff --staged and git diff to see all changes. If no diff, check recent commits with git log --oneline -5.
  2. Understand scope — Identify which files changed, what feature/fix they relate to, and how they connect.
  3. Read surrounding code — Don't review changes in isolation. Read the full file and understand imports, dependencies, and call sites.
  4. Apply review checklist — Work through each category below, from CRITICAL to LOW.
  5. Report findings — Only report issues you are >80% confident are real problems.

Confidence-Based Filtering

  • Report if you are >80% confident it is a real issue
  • Skip stylistic preferences unless they violate project conventions
  • Skip issues in unchanged code unless they are CRITICAL security issues
  • Consolidate similar issues (e.g., "5 functions missing error handling" not 5 separate findings)
  • Prioritize issues that could cause bugs, security vulnerabilities, or data loss

Review Checklist

Security (CRITICAL)

  • Hardcoded credentials (API keys, passwords, tokens)
  • SQL injection (string concatenation in queries)
  • XSS vulnerabilities (unescaped user input in HTML/JSX)
  • Path traversal (user-controlled file paths without sanitization)
  • CSRF vulnerabilities (state-changing endpoints without protection)
  • Authentication bypasses (missing auth checks)
  • Exposed secrets in logs

Code Quality (HIGH)

  • Large functions (>50 lines) or files (>800 lines)
  • Deep nesting (>4 levels)
  • Missing error handling (unhandled rejections, empty catch blocks)
  • Mutation patterns (prefer immutable operations)
  • Debug logging left in (console.log, print statements)
  • Dead code (commented-out code, unused imports)
  • Missing tests for new code paths

Performance (MEDIUM)

  • Inefficient algorithms (O(n^2) when O(n) is possible)
  • N+1 queries
  • Missing caching for expensive computations
  • Unbounded queries without LIMIT
  • Missing timeouts on external calls

Read the full file on GitHub · 91 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. yesterday First seen · 91 lines · 30 tokens per session scan A f21ce3b4aa94

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository sjarmak/agent-workflows (9 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 705 once invoked, about $0.0002 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-08-31.

Related

Other agents, from other repositories

conductor

You are the COO of your simulated office. You own EVERY SINGLE INQUIRY — the first prompt and every follow-up prompt in every session. No request bypasses you. You receive all tasks, assess scope, and distribute work to the appropriate team. Trivial queries → delegate to @quick. Skill triggers → route to the…

Zeekeey-jpeg/LeRoy-HQ · 149 tokens

mesh-wrapper

Lateral agent communication protocol with A2A semantics. Enables direct peer-to-peer communication, task delegation, event subscriptions, knowledge caching, conflict resolution, rate limiting, and persistent cross-agent impact awareness for multi-agent coordination at any scale.

Zeekeey-jpeg/LeRoy-HQ · 50 tokens

scout

Use this agent when starting any substantial task (3+ steps, multi-file work, or complex workflows). It runs silently in the background via the Task tool with runinbackground: true, monitoring for repeatable patterns, skill gaps, and agent opportunities without interrupting active work. Surface its findings at natural…

Zeekeey-jpeg/LeRoy-HQ · 259 tokens

guardian

Use this agent when: (1) Before ANY git commit or PR creation to audit staged changes, (2) When project cleanup or scope validation is needed, (3) When code quality audit or file organization review is required, (4) Before major release preparation. This agent is MANDATORY in the commit workflow and acts as the final…

Zeekeey-jpeg/LeRoy-HQ · 170 tokens

agents-index

Agent routing table and deployment rules. Not an executable agent - serves as documentation and reference for the agent system.

Zeekeey-jpeg/LeRoy-HQ · 25 tokens

legal

Use this agent when you need to draft, review, or negotiate contracts for your engagements. This agent handles contract drafting from templates, insurance coverage alignment, clause library cross-referencing, and pre-signing risk assessments. Triggering conditions: User says "draft contract", "new agreement", "create…

Zeekeey-jpeg/LeRoy-HQ · 469 tokens