A review command for changed shell scripts, which are files containing terminal commands. It checks security, common shell mistakes, code quality, and runs ShellCheck, a tool that detects shell-script problems.

Use it to review recently changed .sh or .bash files, report findings with line numbers, run ShellCheck, and give an approve, changes-needed, or block verdict.

It helps catch unsafe input handling, exposed credentials, quoting mistakes, and other issues before changed scripts are accepted.

How mylee04/who-ran-what configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to mylee04/who-ran-what. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/mylee04/who-ran-what/main/.claude/commands/review.md

Clone the repo

git clone --depth 1 https://github.com/mylee04/who-ran-what

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/mylee04/who-ran-what/review/github.svg)](https://agentmods.dev/commands/mylee04/who-ran-what/review)

Your own site

<a href="https://agentmods.dev/commands/mylee04/who-ran-what/review"><img src="https://agentmods.dev/badge/commands/mylee04/who-ran-what/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/mylee04/who-ran-what/review"><img src="https://agentmods.dev/badge/commands/mylee04/who-ran-what/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 296 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.

Model	Per session	Once invoked
Fable 5.1	$0.00008	$0.00296
Opus 5.5	$0.00003	$0.00118
Sonnet 5.5	$0.00002	$0.00059
Haiku 4.5	$0.00001	$0.00030

Measured 1mo ago against content hash 6553b1c5f85a, 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 1mo 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.

.claude/commands/review.md · 52 lines

What it actually says

Code Review

Execute these steps NOW:

Step 1: Identify changed files

git diff --name-only HEAD~1 | grep -E '\.(sh|bash)$' || git diff --name-only HEAD~1

Step 2: For each changed file, check:

Security (BLOCK if found)

No hardcoded credentials or API keys
No eval on user input
No command injection vulnerabilities

Shell Best Practices (NEEDS CHANGES if found)

All variables quoted: "$var"
Functions use local for variables
Uses [[ ]] not [ ]
Uses command -v not which

Code Quality

Functions are small and focused
Variable names are clear
No dead code

Step 3: Output format

## Code Review: [filename]

### Security: ✅ PASS / ❌ ISSUES
[list any issues]

### Best Practices: ✅ PASS / ⚠️ WARNINGS
[list any issues with line numbers]

### Verdict: APPROVE / NEEDS CHANGES / BLOCK

Step 4: Run shellcheck

shellcheck -x -e SC1091 [changed files]

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.

1mo ago First seen · 52 lines · 8 tokens per session scan A 6553b1c5f85a

Subscribe to this mod's changes

review is a command published in the GitHub repository mylee04/who-ran-what (3 stars, last pushed 8mo ago), licensed MIT. It adds 8 tokens to every session and 296 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-31.

ai claude cli codex developer-tools

who-ran-what: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Code Review

Step 1: Identify changed files

Step 2: For each changed file, check:

Security (BLOCK if found)

Shell Best Practices (NEEDS CHANGES if found)

Code Quality

Step 3: Output format

Step 4: Run shellcheck

What this file has done since we first saw it

Other commands, from other repositories

review-branch

security

commit

modernize-transform

amp-register

react-native