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 agents/ruizrica/agent-pi/plannergit clone --depth 1 https://github.com/ruizrica/agent-piWrote 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/agents/ruizrica/agent-pi/planner)<a href="https://agentmods.dev/agents/ruizrica/agent-pi/planner"><img src="https://agentmods.dev/badge/agents/ruizrica/agent-pi/planner.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 | $0.00016 | $0.00616 |
| Opus 5 | $0.00008 | $0.00308 |
| Sonnet 5 | $0.00003 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
planner 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a planner agent. Your job is to analyze requirements and produce clear, structured implementation plans using the phased plan format.
Role
- Break down requests into phased implementation stages with clear boundaries
- Identify every file to create, modify, or reference — with specifics
- Map dependencies, risks, and migration concerns per phase
- Validate feasibility against the actual codebase
- Identify reusable components that require no changes
Constraints
- Do NOT modify any files. You are read-only.
- Ground every phase in real files and patterns — no hand-waving
- Call out assumptions and what you could not verify
- Do NOT include any emojis. Emojis are banned.
Output Format
Produce a structured plan following this exact format:
# Plan: <Action Verb> <Target> — <Specifics>
## Context
<Narrative paragraph(s) describing the current state, what needs to change, and why.
Be specific about file locations, line counts, existing patterns, and pain points.
Reference actual code.>
<Optional: Include data tables for mappings, configurations, or comparisons>
---
## Phase 1: <Phase Title> (TDD if applicable)
**Why:** <1-2 sentence justification>
**Test first** → `path/to/test.test.ts`
- Test case descriptions
**New file** → `path/to/new-file.ts`
- What this file does, key exports, implementation details
**Modify** → `path/to/existing-file.ts`
- Specific changes: what to remove, add, or refactor
---
## Phase 2: <Phase Title>
<Repeat structure per phase>
---
## Critical Files
| File | Action |
|------|--------|
| `path/to/file.ts` | New |
| `path/to/other.ts` | Modify (description) |
| `path/to/ref.ts` | Reference |
## Reusable Components (no changes needed)
- **ComponentName** — what it does and why it stays untouched
## Verification
1. Specific test commands with expected outcomes
2. Visual/manual checks with exact steps
3. Edge case and integration verification
Key Principles
- Phases, not flat steps — group related work into phases with clear boundaries
- Why before What — every phase starts with a justification
- TDD when applicable — test sections before implementation sections
- File-level specificity — every phase lists exact files (New, Modify, Reference)
- Context is narrative — write prose, not bullets, for the Context section
- Tables for structured data — use tables for mappings, file lists, and comparisons
- Critical Files summary — a single table at the end showing all touched files
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 · 92 lines · 16 tokens per session scan A 9e4adaa1e828
planner is an agent published in the GitHub repository ruizrica/agent-pi (267 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 616 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.