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 pueraeternis/agentic-project-template --skill 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/skills/pueraeternis/agentic-project-template/plan-review)<a href="https://agentmods.dev/skills/pueraeternis/agentic-project-template/plan-review"><img src="https://agentmods.dev/badge/skills/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.
<a href="https://agentmods.dev/skills/pueraeternis/agentic-project-template/plan-review"><img src="https://agentmods.dev/badge/skills/pueraeternis/agentic-project-template/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.00000 | $0.00803 |
| Opus 5 | $0.00000 | $0.00402 |
| Sonnet 5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00080 |
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 8d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Review
Purpose
This skill validates an implementation plan before implementation begins.
The review confirms that the plan is complete, consistent, traceable, and ready for execution.
Plan Review is the final quality gate before implementation authorization.
Lifecycle Stage
Plan Creation
↓
Plan Review
↓
Plan Implementation
Plan Review determines whether implementation can safely begin.
Role
Primary role:
Review Agent
When to Use
Use this skill when:
- a new implementation plan has been created;
- an implementation plan has been significantly revised;
- implementation authorization is required.
Always perform this review before implementation begins.
Inputs
Required:
- implementation plan;
PROJECT.md;ROADMAP.md;ARCHITECTURE.md;ENGINEERING.md.
Additional references:
- ADRs;
- completed plans;
- current repository state (when relevant).
The implementation plan is the proposed engineering contract.
Outputs
Produce one review outcome:
- Approved
- Approved with Minor Suggestions
- Changes Requested
When revisions are required, provide clear, prioritized, and actionable feedback.
Procedure
Step 1 — Build Context
Review:
- project definition;
- roadmap;
- architecture;
- engineering design;
- ADRs;
- completed plans.
Understand why this implementation increment exists.
Step 2 — Verify Scope
Confirm that:
- scope is explicit;
- implementation boundaries are clear;
- work fits the current roadmap phase;
- engineering conventions are respected;
- undocumented work has not been introduced.
Every major implementation item should be traceable to approved project documentation.
Step 3 — Verify Completeness
Confirm the plan contains:
- objective;
- scope;
- out-of-scope items;
- acceptance criteria;
- validation strategy;
- implementation checklist;
- identified risks.
Implementation should not require inventing missing requirements.
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.
- 8d ago First seen · 243 lines · 0 tokens per session scan A 2beafafdc19e
plan-review is a skill 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 803 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 skills, from other repositories
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
lithium-kb
Generates, maintains, and visualizes a structured Markdown knowledge base (.lithium-kb/{architecture,debug,tasks,features}) with an interactive Neural Network graph, auto-watch mode, custom agent directives (.agentrules), and MCP server integration for Pi, Claude, Codex, Cursor, and other coding agents. Triggers…
Brainstorming & Architectural Design
Interactive design process to explore architecture, requirements, and user experience before writing code.
Systematic Debugging
Scientific root-cause isolation and step-by-step resolution of complex runtime bugs.
Subagent Driven Development
Orchestrate specialized, autonomous AI agents to execute parallel subtasks with strict boundaries.
Test Driven Development
Strict Red-Green-Refactor implementation methodology for high quality, regression-free software.