review

review is a command for coding agents from owainlewis/youtube-tutorials. It costs 0 tokens per session (202 once invoked), scanned A, original, MIT.

A command for reviewing code like a senior engineer, focusing on simplicity, readability, consistency, and correctness. It can inspect specified files or all currently changed files.

In plain words
What is it for?
Use it to check for edge cases, unnecessary abstractions, unclear names, inconsistent patterns, and other issues, with file locations and replacement code when changes are needed.
Why use it?
It helps find real bugs and confusing code without encouraging unnecessary rewrites. The review is meant to be understandable to a new teammate and aligned with the project's conventions.

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/owainlewis/youtube-tutorials/review
Clone the repo
git clone --depth 1 https://github.com/owainlewis/youtube-tutorials

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/owainlewis/youtube-tutorials/review.svg)](https://agentmods.dev/commands/owainlewis/youtube-tutorials/review)
Your own site
<a href="https://agentmods.dev/commands/owainlewis/youtube-tutorials/review"><img src="https://agentmods.dev/badge/commands/owainlewis/youtube-tutorials/review.svg" alt="Measured on agentmods" height="20"></a>
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 202 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.00202
Opus 5 $0.00000 $0.00101
Sonnet 5 $0.00000 $0.00040
Haiku 4.5 $0.00000 $0.00020

Measured 4d ago against content hash 05222f442d3f, 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.

tutorials/spec-driven-development/resources/commands/review.md · 47 lines

What it actually says

Review

Review code as a senior engineer would.

Target

$ARGUMENTS

If no target specified, review all changed files.

Instructions

Look at the code and ask:

Simplicity

  • Is this over-engineered?
  • Could it be shorter without losing clarity?
  • Are there unnecessary abstractions?

Clarity

  • Are names descriptive?
  • Is the logic easy to follow?
  • Would a new teammate understand this?

Consistency

  • Does it match patterns in CLAUDE.md?
  • Is it idiomatic for the language?

Correctness

  • Are edge cases handled?
  • Any obvious bugs?

Output

If changes needed:

  1. List specific issues with file and line
  2. Provide the fixed code

If code is good:

  • Say so briefly and move on

Guidelines

  • Be constructive, not nitpicky
  • Focus on what matters: bugs, clarity, maintainability
  • Don't suggest changes just to suggest changes
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 · 47 lines · 0 tokens per session scan A 05222f442d3f

Subscribe to this mod's changes

review is a command published in the GitHub repository owainlewis/youtube-tutorials (378 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 202 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.