A review process for engineering plans before a feature, refactor, or major code change is implemented. It examines the actual codebase and records issues and decisions.

Use it to inspect a proposed implementation plan, verify how it fits the existing project, and decide what should happen before coding begins.

It helps catch missing connections, repeated logic, unneeded complexity, and edge cases before code is changed.

plan-review — Skill for Claude Code by 0xUXDesign

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.

Any agent

npx skills add 0xUXDesign/ai-codebase-boilerplate --skill plan-review

Clone the repo

git clone --depth 1 https://github.com/0xUXDesign/ai-codebase-boilerplate

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/skills/0xuxdesign/ai-codebase-boilerplate/plan-review.svg)](https://agentmods.dev/skills/0xuxdesign/ai-codebase-boilerplate/plan-review)

Your own site

<a href="https://agentmods.dev/skills/0xuxdesign/ai-codebase-boilerplate/plan-review"><img src="https://agentmods.dev/badge/skills/0xuxdesign/ai-codebase-boilerplate/plan-review.svg" alt="Measured on agentmods" height="20"></a>

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,229 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.00049	$0.01229
Opus 5	$0.00024	$0.00615
Sonnet 5	$0.00010	$0.00246
Haiku 4.5	$0.00005	$0.00123

Measured 7d ago against content hash ab8153a49b72, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

plan-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 7d 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.

skills/plan-review/SKILL.md · 112 lines

How it starts

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

Plan Review

You are now in plan mode. Do NOT make any code changes. Think, evaluate, and present decisions.

Document Review

If the user provides a document, PRD, prompt, or artifact alongside this command, that IS the plan to review. Apply all review sections to that document. Do not treat it as background context — it is the subject of evaluation.

Project Overrides

If a .claude/plan-review.md file exists in this project, read it now and apply those rules on top of this baseline. Project rules take precedence where they conflict.

Engineering Preferences (guide all recommendations)

DRY: flag repetition aggressively
Well-tested: too many tests > too few; mutation score > line coverage
"Engineered enough" — not fragile/hacky, not over-abstracted
Handle more edge cases, not fewer; thoughtfulness > speed
Explicit > clever; simple > complex
Subtraction > addition; target zero or negative net LOC
Every export must have a caller; unwired code doesn't exist

Step 1: Pharaoh Reconnaissance (Required — do this BEFORE reviewing)

Do NOT review from memory or assumptions. Query the actual codebase first:

get_codebase_map — current modules, hot files, dependency graph
search_functions for keywords related to the plan — find existing code to reuse/extend
get_module_context on affected modules — entry points, patterns, conventions
query_dependencies between affected modules — coupling, circular deps

Ground every recommendation in what actually exists. If you propose adding something, confirm it doesn't already exist. If you propose changing something, know its blast radius.

Step 2: Mode Selection

Ask the user which mode before starting the review:

BIG CHANGE: Full interactive review, all relevant sections, up to 4 top issues per section. SMALL CHANGE: One question per section, only sections 2-4.

Step 3: Review Sections

Adapt depth to change size. Skip sections that don't apply.

Section 1 — Architecture (skip for small/single-file changes)

Read the full file on GitHub · 112 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

plan-review-override-template.md 933 B

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.

7d ago First seen · 112 lines · 49 tokens per session scan A ab8153a49b72

Subscribe to this mod's changes

plan-review is a skill published in the GitHub repository 0xUXDesign/ai-codebase-boilerplate (11 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 1,229 once invoked, about $0.0002 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-30.

Claude Code Planning ai-coding biome code-quality developer-tools knip

ring:migrating-to-lib-observability

Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…

LerianStudio/ring · 104 tokens

ring:using-lib-systemplane

Using lib-systemplane, the hot-reload runtime-config plane (Postgres LISTEN/NOTIFY or MongoDB change streams), in two modes. Sweep Mode detects DIY config reload (SIGHUP, fsnotify, viper, pgx LISTEN), manual tenant-scoping, hand-built admin CRUD, and v4 residue. Reference Mode catalogs client lifecycle and…

LerianStudio/ring · 106 tokens

ring:adopting-lib-commons-huma-wrapper

Adopting the lib-commons/v5 shared Huma (OAS 3.1) OpenAPI wrapper + RFC 9457 problem model (commons/net/http/{openapi,problem}) in a Lerian Go service: wire openapi.New/ServeSpec + problem.Install (central >=500 scrub) on BOTH runtime and spec-gen paths, the per-rail problem.MapError flex seam, and rename-only spec…

LerianStudio/ring · 142 tokens

ring:applying-composition-patterns

React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…

LerianStudio/ring · 68 tokens

ring:using-lib-observability

Using lib-observability v1.1.0, Lerian's OpenTelemetry foundation (lib-commons, lib-systemplane, lib-streaming depend on it), in two modes. Sweep Mode detects DIY zap/slog logging, raw OTel metrics, hand-rolled redaction, and hard-coded attribute strings. Reference Mode catalogs the log, metrics, zap, redaction, and…

LerianStudio/ring · 102 tokens

ring:using-outbox

Using the transactional-outbox pattern across lib-streaming (writer) and lib-commons/v5/commons/outbox (repository + relay), in two modes. Sweep Mode detects DIY outbox tables, hand-rolled relay loops, send-and-pray emits, missing WithOutboxTx wrapping, and broker calls inside DB transactions. Reference Mode catalogs…

LerianStudio/ring · 98 tokens