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 agentmods add commands/xiaolai/cc-suite/review-plangit clone --depth 1 https://github.com/xiaolai/cc-suiteWrote 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/commands/xiaolai/cc-suite/review-plan)<a href="https://agentmods.dev/commands/xiaolai/cc-suite/review-plan"><img src="https://agentmods.dev/badge/commands/xiaolai/cc-suite/review-plan.svg" alt="Measured on agentmods" 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.00021 | $0.01287 |
| Opus 5 | $0.00010 | $0.00643 |
| Sonnet 5 | $0.00004 | $0.00257 |
| Haiku 4.5 | $0.00002 | $0.00129 |
Grade A, and why
review-plan 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
When to Use
Use /review-plan when:
- A plan will drive more than 2 hours of implementation work
- The plan touches multiple subsystems or shared interfaces
- You want an independent read on feasibility before delegating to Codex
- A prior implementation attempt failed and you suspect the plan was at fault
What This Does
Sends a plan document to Codex running in an isolated context for independent review. Codex reads the plan (and optional context files), then evaluates it across 5 dimensions that matter for plans — not code quality, but buildability.
Model & Settings Selection
Follow the instructions in commands/shared/model-selection.md to discover available models and present choices.
- Recommended model: first available from preflight
- Recommended reasoning effort:
high - Include sandbox question: No (plan review always uses
read-only)
Workflow
Step 0: Parse Execution Mode
Parse $ARGUMENTS for --background or --wait flags (remove the flag from remaining arguments):
| Flag | Mode |
|---|---|
--background |
Background — spawn detached Codex runner, return job ID |
--wait |
Foreground (explicit) — same as default |
| Neither | Foreground (default) — run inline, block until complete |
Step 1: Determine Scope
Parse $ARGUMENTS to find the plan:
| Input | Interpretation |
|---|---|
| (empty) | Look for dev-memo/plan.md, then plan.md, then ask |
path/to/plan.md |
Use that file |
path/to/plan.md +context1.md +context2.md |
Plan file + additional context files |
Read the plan file. If the specified file does not exist, report "Plan file not found: {path}" and stop. If it references other documents (design docs, specs, AGENTS.md), read those too — they become context.
Step 2: Send Plan for Review
If --background mode was selected, follow the Background Execution section in commands/shared/codex-call.md. Build the prompt as described below, then hand off to the background runner with --kind review-plan.
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.
- 5d ago First seen · 155 lines · 21 tokens per session scan A 6dcde711edf4
review-plan is a command published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 3d ago), licensed ISC. It adds 21 tokens to every session and 1,287 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-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.