plan-review

A review step for checking a written coding plan with GPT before work begins. It can use the plan file or the current conversation.

In plain words
What is it for?
Use it to get independent feedback on a plan and receive a go-or-no-go recommendation.
Why use it?
It helps catch missing steps, conflicts with existing code, and other problems before implementation starts.

Skill for Claude CodeCodex

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 skills/dr-code/tessera/plan-review
Any agent
npx skills add dr-code/tessera --skill plan-review
Clone the repo
git clone --depth 1 https://github.com/dr-code/tessera

Made for: Claude Code, Codex.

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 680 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.00030 $0.00680
Opus 5 $0.00015 $0.00340
Sonnet 5 $0.00006 $0.00136
Haiku 4.5 $0.00003 $0.00068

Measured yesterday against content hash ea3df69358cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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 · 64 lines

How it starts

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

/plan-review — Independent Plan Review via Codex

Usage

/plan-review path/to/plan.md /plan-review — reads plan from current conversation context or asks user to provide it

Description

Send an implementation plan to GPT via Codex CLI for structured review before implementation begins. Claude synthesizes GPT's feedback, agrees or disagrees with each point, and issues a go/no-go verdict.

Instructions

Phase 0: Load Plan + Tessera Context

If tessera MCP is configured in this session:

1. graph_continue (mandatory first call)
2. graph_action_summary — surface locked decisions that may constrain the plan
3. graph_retrieve with the plan's key feature terms — find relevant existing code
  • If a file path was provided: read the plan file
  • If no path: ask the user to paste the plan or specify where it is
  • Include the retrieved context and any locked decisions in the GPT review prompt so it can flag contradictions with existing patterns

Phase 1: Send to GPT

Construct the review prompt with the full plan text and any codebase context:

codex exec "You are reviewing an implementation plan before execution begins. Plan: <PLAN_TEXT>. Codebase context: <CONTEXT>. Review for: (1) architecture violations or inconsistency with existing patterns, (2) missing edge cases or error handling, (3) wrong ordering of steps or missing dependencies between steps, (4) security concerns, (5) over-engineering or unnecessary complexity. For each issue: ISSUE: <description> | SUGGEST: <specific fix> | SEVERITY: HIGH/MED/LOW. End with VERDICT: approved OR needs_revision"

Phase 2: Claude Synthesizes

For each GPT issue, Claude responds:

  • AGREE — the plan needs to change here; note what revision is required
  • DISAGREE — explain why the plan already handles it or why GPT's concern is inapplicable
  • PARTIAL — the concern is valid but the suggested fix is wrong; propose a better fix

Phase 3: Output

Read the full file on GitHub · 64 lines

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. yesterday First seen · 64 lines · 30 tokens per session scan A ea3df69358cf

Subscribe to this mod's changes

plan-review is a skill published in the GitHub repository dr-code/tessera (1 stars, last pushed 21d ago), licensed MIT. It adds 30 tokens to every session and 680 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens