code-review

A command for reviewing a pull request, which is a proposed set of code changes awaiting approval. It organizes the review by type of concern and keeps only findings supported by evidence.

In plain words
What is it for?
Use it to review code changes for separate concerns such as correctness, security, maintainability, and testing, then combine the confirmed findings.
Why use it?
It provides a structured way to assess a change without overlooking important issues or reporting unsupported complaints.

Command

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/bearlike/assistant/code-review
Clone the repo
git clone --depth 1 https://github.com/bearlike/Assistant
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 47 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.00005 $0.00047
Opus 5 $0.00003 $0.00023
Sonnet 5 $0.00001 $0.00009
Haiku 4.5 $0.00001 $0.00005

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

demo/plugins/cache/claude-plugins-official/code-review/unknown/commands/code-review.md · 10 lines

What it actually says

Code Review

Split the review by dimension rather than by file, then merge the findings and drop everything the evidence does not carry.

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 · 10 lines · 5 tokens per session scan A 76d7c0cd42bd

Subscribe to this mod's changes

code-review is a command published in the GitHub repository bearlike/Assistant (41 stars, last pushed 7d ago), licensed MIT. It adds 5 tokens to every session and 47 once invoked, about $0.0000 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-30.