agentmods.dev

code-review

A command that checks uncommitted code changes for security problems, quality issues, and common signs of unfinished or misleading code.

In plain words
What is it for?
Use it to review the files changed since the last commit. It reports severity, file locations, explanations, and suggested fixes, and blocks on critical or high-priority findings.
Why use it?
It catches risks such as exposed credentials, unsafe input handling, missing error handling, and invalid imports before the changes are accepted.

Command

2 5mo ago A scan 20 tokens original MIT
View the source file zhmxiaowo/opencode-simple
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 commands/zhmxiaowo/opencode-simple/code-review
Clone the repo
git clone --depth 1 https://github.com/zhmxiaowo/opencode-simple
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 333 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.00020 $0.00333
Opus 5 $0.00010 $0.00167
Sonnet 5 $0.00004 $0.00067
Haiku 4.5 $0.00002 $0.00033

Measured yesterday against content hash b56643db5cf1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.opencode/commands/code-review.md · 52 lines

What it actually says

Code Review

Comprehensive security and quality review of uncommitted changes:

  1. Get changed files: git diff --name-only HEAD

  2. For each changed file, check for:

Security Issues (CRITICAL):

  • Hardcoded credentials, API keys, tokens
  • SQL injection vulnerabilities
  • XSS vulnerabilities
  • Missing input validation
  • Insecure dependencies
  • Path traversal risks

Code Quality (HIGH):

  • Functions > 50 lines
  • Files > 800 lines
  • Nesting depth > 4 levels
  • Missing error handling
  • console.log statements
  • TODO/FIXME comments
  • Missing JSDoc for public APIs

Best Practices (MEDIUM):

  • Mutation patterns (use immutable instead)
  • Emoji usage in code/comments
  • Accessibility issues (a11y)
  • Missing SPEC.md for new features (Spec-First principle)

AI Slop (MEDIUM):

  • Placeholder comments: // TODO: implement, // Add code here, // ... rest of
  • Hallucinated imports (modules not in project deps)
  • Empty function bodies or unreachable code
  • Overly verbose/obvious comments that just repeat the code

  1. Generate report with:

    • Severity: CRITICAL, HIGH, MEDIUM, LOW
    • File location and line numbers
    • Issue description
    • Suggested fix

  2. Block commit if CRITICAL or HIGH issues found

Never approve code with security vulnerabilities!

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 · 52 lines · 20 tokens per session scan A b56643db5cf1

Subscribe to this mod's changes

code-review is a command published in the GitHub repository zhmxiaowo/opencode-simple (2 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 333 once invoked, about $0.0001 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.

Code reviewGit and workflowSecurity
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens