agentmods.dev

review

A command for reviewing code changes and reporting problems or improvements. It can inspect staged changes, a file’s differences, or a pull request, which is a proposed code change for team review.

In plain words
What is it for?
Use it to review staged work, a specific file, or a pull request for bugs, unsafe practices, missing validation, hardcoded values, and style or typing problems.
Why use it?
It provides a repeatable review covering project standards, code quality, error handling, and security. This helps catch issues before changes are merged.

Command

57 8d ago A scan 0 tokens original MIT
View the source file intellegix/intellegix-code-agent-toolkit
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/intellegix/intellegix-code-agent-toolkit/review
Clone the repo
git clone --depth 1 https://github.com/intellegix/intellegix-code-agent-toolkit
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,055 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.01055
Opus 5 $0.00000 $0.00528
Sonnet 5 $0.00000 $0.00211
Haiku 4.5 $0.00000 $0.00105

Measured 2d ago against content hash b221b64d4631, 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 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.

commands/review.md · 192 lines

How it starts

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

Code Review

Review the code changes and provide detailed feedback.

Target: $ARGUMENTS

If no target specified, review staged changes: git diff --cached

Review Process

Step 1: Gather Context

  1. Get the diff

    # If PR number provided
gh pr diff $ARGUMENTS

# If file path provided
git diff HEAD -- $ARGUMENTS

# If no argument, staged changes
git diff --cached

  2. Understand the context

    • What is this change trying to accomplish?
    • Check related issues/PRs if mentioned
    • Review commit messages

Step 2: Code Quality Review

  1. Check against project standards

    • Follows naming conventions (see CLAUDE.md Section 1)
    • Proper error handling with Result pattern
    • No hardcoded values that should be config
    • No commented-out code or debug statements

  2. TypeScript/Python specific

    • Explicit return types on exported functions
    • No any types (use unknown if truly needed)
    • Proper null/undefined handling
    • Type hints on all functions (Python)

Step 3: Security Review

  1. Security checklist
    • No secrets or credentials in code
    • Input validation for external data
    • Proper authentication/authorization checks
    • No SQL injection vulnerabilities
    • No XSS vulnerabilities (if frontend)

Step 4: Testing Review

  1. Test coverage
    • New code has corresponding tests
    • Edge cases covered
    • Tests are readable and test behavior (not implementation)
    • Mocks used appropriately

Step 5: Performance Review

  1. Performance checklist
    • No obvious N+1 query issues
    • Appropriate use of async/await
    • No unnecessary re-renders (React)
    • Large lists virtualized
    • No memory leaks (cleanup in useEffect)

Step 6: Portfolio Compliance Review

  1. Over-engineering check
    • Read ~/.claude/portfolio/PORTFOLIO.md
    • Is complexity appropriate for this project's tier and user count?
    • Are there enterprise patterns that don't belong at this scale?
    • Does the change respect phase restrictions?
    • Flag over-engineering as a "Must Fix" issue.

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

Subscribe to this mod's changes

review is a command published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,055 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.

Code reviewDebuggingProductivityagentic-aiai-agentsanthropicautomationclaudeclaude-code
Related

Other commands, from other repositories

README

Git workflow and quality assurance commands for the claude-skills repository.

alirezarezvani/claude-skills · 0 tokens

agentlas-cloud

Staff a task only from the signed-in owner's Agent Cloud agents.

agentlas-ai/Agentlas-OS · 13 tokens

dispatcher

Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.

Kanevry/session-orchestrator · 31 tokens

tldr

Re-apply TLDR rules for this turn (verdict first, no filler).

0p9b/TLDR · 17 tokens

me-figure-discussion

Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.

hanhuark/mechanical-engineering-research-skill · 21 tokens

execute

Interactive workflow for workspace isolation, pane-delegated implementation, testing, review, and cleanup.

transparent-pegasus/herdrpowers · 18 tokens