agentmods.dev

review

review is a command for Claude Code from d-padmanabhan/agent-engineering-handbook. It costs 9 tokens per session (547 once invoked), scanned A, original, MIT.

A code-review workflow that checks whether an implementation matches its approved plan and follows project rules.

In plain words
What is it for?
Use it to review a pull request or completed coding task, check correctness and quality, and document findings for future work.
Why use it?
It helps catch bugs, security problems, missing tests, unrelated edits, and other issues before changes are accepted. It records suggestions without changing the implementation.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

not rated 20repo yesterday A scan 9 tokens original MIT

Good fit Use it to review a pull request or completed coding task, check correctness and quality, and document findings for future work.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/d-padmanabhan/agent-engineering-handbook/review
View source ↗ d-padmanabhan/agent-engineering-handbook
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.

Clone the repo
git clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbook

Made for: Claude Code.

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/d-padmanabhan/agent-engineering-handbook/review/github.svg)](https://agentmods.dev/commands/d-padmanabhan/agent-engineering-handbook/review)
Your own site
<a href="https://agentmods.dev/commands/d-padmanabhan/agent-engineering-handbook/review"><img src="https://agentmods.dev/badge/commands/d-padmanabhan/agent-engineering-handbook/review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for review

Your own site · 80×15
<a href="https://agentmods.dev/commands/d-padmanabhan/agent-engineering-handbook/review"><img src="https://agentmods.dev/badge/commands/d-padmanabhan/agent-engineering-handbook/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 547 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00009 $0.00547
Opus 5.5 $0.00004 $0.00219
Sonnet 5.5 $0.00002 $0.00109
Haiku 4.5 $0.00001 $0.00055

Measured 2mo ago against content hash 6bcb1eecdb58, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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 · 101 lines

How it starts

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

REVIEW MODE ACTIVATED

You are now in REVIEW phase.

Your Tasks

  1. Verify Implementation

    • Check that changes match the approved plan
    • Ensure all planned items are complete
    • Confirm no unrelated changes were made

  2. Check for Issues

    • Security vulnerabilities
    • Bugs or edge cases
    • Performance concerns
    • Error handling gaps

  3. Review Against Standards

    • Code follows 100-core.mdc guidelines
    • Language-specific rules applied
    • Tests added/updated
    • Documentation updated

  4. Suggest Improvements

    • Note potential improvements but DON'T implement them
    • These are for future work, not this PR
    • Prioritize by impact

  5. Update Context Files

    • Document findings in reflect-*.md or tasks.md
    • Note lessons learned

Review Checklist

Correctness

  • Changes match the agreed plan
  • All edge cases handled
  • Error handling appropriate
  • No regressions introduced

Security

  • No hardcoded secrets
  • Input validation present
  • No injection vulnerabilities
  • Principle of least privilege followed

Quality

  • Code follows existing patterns
  • Naming is clear and consistent
  • No unnecessary complexity
  • DRY principle followed

Testing

  • Tests added/updated
  • Edge cases covered
  • Tests pass locally

Documentation

  • Code comments where needed
  • README updated if applicable
  • API docs updated if applicable

Output Format

## Review Summary

### What Was Implemented
- [Summary of changes]

### Verification
- [x] Matches approved plan
- [x] All items complete
- [ ] Issue found: [description]

### Issues Found
1. **[Critical/Recommended/Optional]**: [Issue description]
   - Location: `file.py:123`
   - Suggestion: [How to fix]

### Suggested Improvements (Future Work)
- [Improvement 1]
- [Improvement 2]

### Ready to Commit?
[Yes/No - with reasoning]

After Review

If ready to commit, use the Git workflow skill (${HANDBOOK_ROOT}/skills/git-workflow/SKILL.md) for message format and the Git rule (${HANDBOOK_ROOT}/rules/130-git.mdc) for mandatory approval and signing gates.

Read the full file on GitHub · 101 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. 2mo ago First seen · 101 lines · 9 tokens per session scan A 6bcb1eecdb58

Subscribe to this mod's changes

review is a command published in the GitHub repository d-padmanabhan/agent-engineering-handbook (20 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 547 once invoked, about $0.0000 per session on Opus 5.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.

Code review
Related

review compared with commands from other repositories

review next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
reviewd-padmanabhan/agent-engineering-handbookCommand20yesterdayMITA9Claude Code
diff-reviewcoco-research/cocoCommand785yesterdayApache-2.0A11Claude Code
review-branchdamusix/atomic-claudeCommand1155d agoMITA35Claude Code
refactorRchGrav/claudeboxCommand1.2k1mo agoMITA9Claude Code
spec-trace-requirementsrjmurillo/ai-agentsCommand49yesterdayMITA0GitHub Copilot
merge-conflict-analysisrjmurillo/ai-agentsCommand49yesterdayMITA0GitHub Copilot
initazrtydxb/procoderCommand21111d agoApache-2.0A16Claude Code