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.
npx skills add Smirnov-Labs/claude-skills --skill codex-plan-reviewgit clone --depth 1 https://github.com/Smirnov-Labs/claude-skillsWrote 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/skills/smirnov-labs/claude-skills/codex-plan-review)<a href="https://agentmods.dev/skills/smirnov-labs/claude-skills/codex-plan-review"><img src="https://agentmods.dev/badge/skills/smirnov-labs/claude-skills/codex-plan-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.
<a href="https://agentmods.dev/skills/smirnov-labs/claude-skills/codex-plan-review"><img src="https://agentmods.dev/badge/skills/smirnov-labs/claude-skills/codex-plan-review.svg" alt="Reviewed on agentmods" width="80" 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.00072 | $0.00890 |
| Opus 5 | $0.00036 | $0.00445 |
| Sonnet 5 | $0.00014 | $0.00178 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
codex-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 11d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Plan Review
Send the current working plan to Codex 5.4 for an independent second opinion. This skill is used to iterate on plans before committing to implementation.
When to Use
- After brainstorming produces a design spec
- After writing an implementation plan
- When you want a critical review before executing a plan
- When the user says "get a second opinion" or "review this plan"
Process
1. Find the Current Plan
Locate the most recent plan by checking these locations in order:
- Design specs:
docs/superpowers/specs/*.md(most recent by date prefix) - Plan files:
docs/superpowers/plans/*.md(most recent by date prefix) - Active context:
.claude/memory-bank/activeContext.mdfor references to current work
If no plan file is found, ask the user to point you to the plan or spec they want reviewed.
2. Read and Summarize the Plan
Read the full plan file. Construct a prompt for Codex that includes:
- The complete plan content
- The project context (from CLAUDE.md or memory bank if relevant)
- A request for critical architectural review
3. Send to Codex
Run Codex with these exact settings — non-spark model, high effort, read-only:
codex exec \
-m gpt-5.4-codex \
--config model_reasoning_effort="high" \
--sandbox read-only \
--skip-git-repo-check \
--full-auto \
2>/dev/null \
"<prompt>"
The prompt sent to Codex must follow this template:
You are a senior architect reviewing an implementation plan. Your job is to find weaknesses, missing considerations, and improvements. Be direct and specific.
PROJECT CONTEXT:
<brief project description from CLAUDE.md or memory bank>
PLAN TO REVIEW:
<full plan content>
Review this plan and provide:
1. **Structural Issues** — Are there missing steps, wrong ordering, or circular dependencies?
2. **Architectural Concerns** — Does the plan fight existing patterns? Are there simpler approaches?
3. **Risk Assessment** — What could go wrong? What assumptions are fragile?
4. **Missing Considerations** — What did the plan author overlook? (edge cases, error handling, testing, rollback)
5. **Specific Improvements** — Concrete suggestions, not vague advice. Reference specific plan sections.
Be critical. The goal is to strengthen the plan, not validate it.
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.
- 11d ago First seen · 101 lines · 72 tokens per session scan A 6a1f787f184f
codex-plan-review is a skill published in the GitHub repository Smirnov-Labs/claude-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 890 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…