Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Custos/angry-ralph/plugin install angry-ralphWrote 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.
[](https://agentmods.dev/commands/custos/angry-ralph/angry-review)<a href="https://agentmods.dev/commands/custos/angry-ralph/angry-review"><img src="https://agentmods.dev/badge/commands/custos/angry-ralph/angry-review.svg" alt="Measured on agentmods" height="20"></a>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.00017 | $0.00545 |
| Opus 5 | $0.00009 | $0.00272 |
| Sonnet 5 | $0.00003 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
angry-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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/angry-review Command
Unified review command. Pipeline Phase 3 when run in context, or on-demand anytime.
1. Argument Parsing
Parse the first argument as the review target:
plan(default) -- Review the implementation plan.code-- Review the codebase against the plan.section <name>-- Review a specific section against its spec.
If no target, default to plan.
2. Detect Context: Pipeline vs On-Demand
Pipeline (Phase 3): .ralph-state/pipeline.json exists AND current_phase is "review" AND target is plan.
Read pipeline state:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/lib/pipeline.sh read . current_phase
bash ${CLAUDE_PLUGIN_ROOT}/scripts/lib/pipeline.sh read . review_tier
bash ${CLAUDE_PLUGIN_ROOT}/scripts/lib/pipeline.sh read . available_reviewers
bash ${CLAUDE_PLUGIN_ROOT}/scripts/lib/pipeline.sh read . max_review_iterations
On-demand: Everything else.
Pipeline Mode (Phase 3)
- Follow the angry-ralph skill's Phase 3 (ADVERSARIAL REVIEW) procedure.
- On completion:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/lib/pipeline.sh write_done . review
bash ${CLAUDE_PLUGIN_ROOT}/scripts/lib/pipeline.sh write . current_phase split
bash ${CLAUDE_PLUGIN_ROOT}/scripts/lib/pipeline.sh append . completed_phases review
On-Demand Mode
- If
.ralph-state/pipeline.jsonexists, readreview_tierandavailable_reviewers. Otherwise runvalidate-env.sh. - Create output directory:
.planning/reviews/on-demand/<target>-<timestamp>/
For plan: Validate .planning/angry-ralph-plan.md exists. Spawn external-reviewer subagent with the plan file.
For code: Validate .planning/angry-ralph-plan.md exists. Spawn external-reviewer subagent for code review against plan.
For section <name>: Resolve .planning/sections/section-<name>.md. Spawn external-reviewer subagent with section spec and changed files.
In all on-demand cases: run triage (CRITICAL/WARNING/INFO), present findings. Do NOT write .done markers.
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.
- 8d ago First seen · 58 lines · 17 tokens per session scan A de8f2cc621fa
angry-review is a command published in the GitHub repository Custos/angry-ralph (5 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 545 once invoked, about $0.0001 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.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.