agentmods.dev

review

review is a command for coding agents from lugassawan/swe-workbench. It costs 72 tokens per session (4,065 once invoked), scanned A, original, MIT.

A code-review command that examines either your local Git changes or a specific pull request using a general or specialist review focus.

In plain words
What is it for?
Use it to review current work, inspect a pull request, or check whether feedback was addressed in a follow-up review.
Why use it?
It helps find security, accessibility, dependency, performance, test, user-experience, or contributor-trust problems before changes are merged.

Command

Part of the swe-workbench plugin — 60 skills, 25 commands, 32 agents, 4 hooks shipped together

not rated 2 2d ago A scan 72 tokens original MIT
View the source file lugassawan/swe-workbench
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/lugassawan/swe-workbench/review
Clone the repo
git clone --depth 1 https://github.com/lugassawan/swe-workbench

Or install swe-workbench, the plugin that ships this one along with the rest of its 60 skills, 25 commands, 32 agents, 4 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for review

README.md
[![agentmods](https://agentmods.dev/badge/commands/lugassawan/swe-workbench/review.svg)](https://agentmods.dev/commands/lugassawan/swe-workbench/review)
Your own site
<a href="https://agentmods.dev/commands/lugassawan/swe-workbench/review"><img src="https://agentmods.dev/badge/commands/lugassawan/swe-workbench/review.svg" alt="Measured on agentmods" height="20"></a>
Per session 72 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,065 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.00072 $0.04065
Opus 5 $0.00036 $0.02032
Sonnet 5 $0.00014 $0.00813
Haiku 4.5 $0.00007 $0.00407

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

Security

Grade A, and why

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

commands/review.md · 142 lines

How it starts

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

Review code with senior-engineer depth. Two dimensions — fully orthogonal:

  • Auditor axis (--mode): which specialist reviews the diff (general / security / accessibility / dependency / performance / tests / contributor-trust). Auto-inferred from the diff when omitted.
  • Diff-source axis: local working-tree diff vs. PR diff. Determined by the remaining arguments after --mode is stripped.

Step 1 — Argument resolution

Parse $ARGUMENTS left-to-right:

  1. If --check-followup <N> is present (where N is a PR number), strip it and enter Followup mode — see ## Followup mode below. All other flags and argument parsing are skipped.

  2. If a --mode <value> flag is present, extract it and normalize the alias:

    --mode value (and aliases) Normalized mode Delegates to
    general general swe-workbench:reviewer
    security, sec security swe-workbench:security-auditor
    accessibility, a11y accessibility swe-workbench:accessibility-auditor
    dependency, deps dependency swe-workbench:dependency-auditor
    performance, perf performance swe-workbench:performance-tuner
    tests (no short alias — keyword is already short) tests swe-workbench:test-reviewer
    contributor-trust, trust contributor-trust swe-workbench:contributor-auditor
    ux (no short alias) ux swe-workbench:product-designer

    Strip --mode <value> from $ARGUMENTS. Store the normalized mode. If the value is unrecognized, print an error listing valid values and stop.

  3. The remaining $ARGUMENTS (after stripping --mode) flow into diff-source detection:

    • Matches [1-9][0-9]* (stripping a leading # if present) → PR mode with that number.

    • Else, run gh pr view --json number,headRefName 2>/dev/null. If it succeeds (current branch has an open PR), print:

      "Detected PR #N on this branch — review it? Reply yes to enter PR mode, or local to review the local diff instead."

      Wait for the user's reply. yes → PR mode. local (or anything else) → local-diff mode.

    • Else → local-diff mode.

Read the full file on GitHub · 142 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. 4d ago First seen · 142 lines · 72 tokens per session scan A ea5953da1fc0

Subscribe to this mod's changes

review is a command published in the GitHub repository lugassawan/swe-workbench (2 stars, last pushed 2d ago), licensed MIT. It adds 72 tokens to every session and 4,065 once invoked, about $0.0004 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 reviewDesign and UXTestingbashclaude-codeclaude-code-pluginclean-architecturedart
Related

Other commands, from other repositories

verify

Fidelity check — rebuild a page from the extracted tokens, pixel-diff it against the live site, and score how faithfully the tokens capture the design.

Manavarya09/design-extract · 31 tokens

brooks-health

Run a Brooks-Lint codebase health dashboard across all four dimensions.

hyhmrright/brooks-lint · 13 tokens

generate-design-md

Génère un DESIGN.md à la racine du projet à partir du template Claude Craft + analyse des sources UI existantes (Tailwind, tokens, CSS).

TheBeardedBearSAS/claude-craft · 33 tokens

design-tutorial

Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.

Adityaraj0421/naksha-studio · 28 tokens

design-system

Generate design tokens, theme configuration, or extract a design system from existing code or Figma files.

Adityaraj0421/naksha-studio · 20 tokens

figma

Convert a Figma design to production code. Provide a Figma URL or select a node in Figma desktop.

Adityaraj0421/naksha-studio · 23 tokens