review

review is a command for Claude Code from SienkLogic/plan-build-run. It costs 14 tokens per session (33 once invoked), scanned A, original, MIT.

A command that checks whether the finished build matches the plan using automated checks and a guided walkthrough.

In plain words
What is it for?
Use it to verify an implementation against its plan.
Why use it?
It helps find gaps between the intended work and what was actually built.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pbr plugin — 44 skills, 71 commands, 18 agents, 3 hooks shipped together

Good fit Use it to verify an implementation against its plan.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/sienklogic/plan-build-run/review
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/SienkLogic/plan-build-run

Made for: Claude Code.

Or install pbr, the plugin that ships this one along with the rest of its 44 skills, 71 commands, 18 agents, 3 hooks.

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/sienklogic/plan-build-run/review/github.svg)](https://agentmods.dev/commands/sienklogic/plan-build-run/review)
Your own site
<a href="https://agentmods.dev/commands/sienklogic/plan-build-run/review"><img src="https://agentmods.dev/badge/commands/sienklogic/plan-build-run/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/sienklogic/plan-build-run/review"><img src="https://agentmods.dev/badge/commands/sienklogic/plan-build-run/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 33 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.00014 $0.00033
Opus 5 $0.00007 $0.00016
Sonnet 5 $0.00003 $0.00007
Haiku 4.5 $0.00001 $0.00003

Measured 5d ago against content hash 88d237f09489, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 5d 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.

plugins/pbr/commands/review.md · 6 lines

What it actually says

This command is provided by the pbr:review skill.

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. 5d ago First seen · 6 lines · 14 tokens per session scan A 88d237f09489

Subscribe to this mod's changes

review is a command published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 33 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-09-03.

Related

Other commands, from other repositories

especificar

Crear especificaciones Gherkin desde un requerimiento/requisito. Usa cuando el usuario dice "escribir specs", "especificar feature", "crear Gherkin", "escribir requerimientos", "write specs", "requirements to Gherkin", "escribir scenarios", "documentar feature en Gherkin". Genera DBML schema auto-máticamente para…

doncheli/don-cheli-sdd · 90 tokens

implementar

Ejecutar tareas TDD fase por fase dentro de Docker hasta que todos los tests pasen.

doncheli/don-cheli-sdd · 19 tokens

spec-score

Puntuación cuantitativa de calidad de especificaciones (0-100) con 8 métricas. Usa cuando el usuario dice "spec score", "quality score", "spec quality", "completitud de specs", "IEEE 830", "ISO 29148", "spec assessment", "medir calidad specs". Score de 0-100 con 8 métricas: completitud, consistencia, verificabilidad…

doncheli/don-cheli-sdd · 102 tokens

desglosar

Dividir un blueprint técnico en tareas con TDD (RED→GREEN) y marcadores de paralelismo.

doncheli/don-cheli-sdd · 22 tokens

drift

Detectar divergencias entre specs Gherkin e implementación (spec drift). Usa cuando el usuario dice "spec drift", "drift detection", "spec vs código", "conformance check", "spec deviation", "código no matchea specs", "implementation diverged", "spec vs implementation", "verificar specs". Compara features implementadas…

doncheli/don-cheli-sdd · 81 tokens

tea

Testing Autónomo End-to-End (TEA): genera, ejecuta y reporta tests automáticamente. Usa cuando el usuario dice "E2E test", "test end-to-end", "correr tests", "generar tests", "testing suite", "run tests", "automated testing", "pruebas E2E", "test coverage", "regression testing". Detecta el framework de testing del…

doncheli/don-cheli-sdd · 97 tokens