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/pueraeternis/agentic-project-template/plan-reviewgit clone --depth 1 https://github.com/pueraeternis/agentic-project-templateWrote 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/pueraeternis/agentic-project-template/plan-review)<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="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.00000 | $0.00401 |
| Opus 5 | $0.00000 | $0.00200 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
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 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 — 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:
AGENTS.mddocs/project/PROJECT.mddocs/project/ROADMAP.mddocs/project/ARCHITECTURE.mddocs/project/ENGINEERING.md- Relevant ADRs
- 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.
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 · 110 lines · 0 tokens per session scan A c3a98e0782dc
plan-review is a command published in the GitHub repository pueraeternis/agentic-project-template (2 stars, last pushed 2mo 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.
Other commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
api-mock
You are an API mocking expert specializing in creating realistic mock services for development, testing, and demonstration purposes. Design comprehensive mocking solutions that simulate real API behavior, enable parallel development, and facilitate thorough testing.
performance-optimization
Orchestrate end-to-end application performance optimization from profiling to monitoring.
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
data-driven-feature
Build features guided by data insights, A/B testing, and continuous measurement.
accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users.