agentic-project-template: Command for Codex

.codex/prompts/plan-review.md

plan-review is a command for Codex from pueraeternis/agentic-project-template. It costs 0 tokens per session (401 once invoked), scanned A, original, MIT.

A checklist for reviewing an implementation plan before coding begins. It compares the plan with project documentation, architecture, engineering rules, and the current roadmap.

In plain words
What is it for?
Use it to assess whether a plan is complete, appropriately scoped, traceable, and ready for implementation.
Why use it?
It helps catch missing scope, unclear acceptance criteria, unnecessary complexity, or conflicts with project decisions before work starts.

Command for Codex

Written for Codex: installed under .codex/. Also seen: mentions AGENTS.md.

This is pueraeternis/agentic-project-template's own configuration. It tells Codex how to work on agentic-project-template itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentic-project-template configures →

Reuse

Borrowing it

Nothing to install: this file belongs to pueraeternis/agentic-project-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/pueraeternis/agentic-project-template/main/.codex/prompts/plan-review.md
Clone the repo
git clone --depth 1 https://github.com/pueraeternis/agentic-project-template

Made for: Codex.

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 plan-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/pueraeternis/agentic-project-template/plan-review/github.svg)](https://agentmods.dev/commands/pueraeternis/agentic-project-template/plan-review)
Your own site
<a href="https://agentmods.dev/commands/pueraeternis/agentic-project-template/plan-review"><img src="https://agentmods.dev/badge/commands/pueraeternis/agentic-project-template/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.

agentmods 80×15 button for plan-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/pueraeternis/agentic-project-template/plan-review"><img src="https://agentmods.dev/badge/commands/pueraeternis/agentic-project-template/plan-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 401 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.00000 $0.00401
Opus 5.5 $0.00000 $0.00160
Sonnet 5.5 $0.00000 $0.00080
Haiku 4.5 $0.00000 $0.00040

Measured 2mo ago against content hash c3a98e0782dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

.codex/prompts/plan-review.md · 110 lines

How it starts

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

Plan Review Prompt

Review the proposed implementation plan before any code is written.


Objective

Determine whether the plan is ready for implementation.

The review should verify that the plan is:

  • complete;
  • coherent;
  • appropriately scoped;
  • traceable;
  • aligned with project documentation;
  • consistent with engineering decisions.

Repository Context

Review the repository documentation in the following order:

  1. AGENTS.md
  2. docs/project/PROJECT.md
  3. docs/project/ROADMAP.md
  4. docs/project/ARCHITECTURE.md
  5. docs/project/ENGINEERING.md
  6. Relevant ADRs
  7. The implementation plan

Evaluate the plan against the documented project intent, architecture, and engineering conventions.


Review Checklist

Verify that the plan:

  • defines exactly one implementation increment;
  • has explicit scope;
  • identifies out-of-scope work;
  • contains measurable acceptance criteria;
  • includes validation requirements;
  • respects the documented architecture;
  • follows the documented engineering conventions;
  • supports the current roadmap phase;
  • does not introduce unnecessary complexity.

Scope Review

Confirm that:

  • the implementation boundary is clear;
  • no unrelated work has been introduced;
  • future roadmap phases are not included;
  • assumptions are documented;
  • engineering constraints are explicit.

Reject hidden scope expansion.


Engineering Review

Evaluate:

  • clarity;
  • completeness;
  • consistency;
  • implementation feasibility;
  • maintainability;
  • validation strategy.

Use ENGINEERING.md as the source of truth for project-specific engineering conventions.

Prefer the simplest plan that satisfies the documented requirements.


Findings

Classify findings as:

  • Major
  • Minor
  • Suggestion

Only Major findings should block implementation.

Avoid requesting unrelated improvements.


Review Outcome

Conclude with one of:

  • Approved
  • Approved with Minor Suggestions
  • Changes Requested

Explain the reasoning for the outcome.

Read the full file on GitHub · 110 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. 2mo ago First seen · 110 lines · 0 tokens per session scan A c3a98e0782dc

Subscribe to this mod's changes

plan-review is a command published in the GitHub repository pueraeternis/agentic-project-template (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 401 tokens. 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.