planner

planner is an agent for Claude Code from espennilsen/pi. It costs 9 tokens per session (262 once invoked), scanned A, original, MIT.

An implementation-planning agent turns requirements and project context into a written plan. It describes the work, files, dependencies, risks, and tests without changing the project.

In plain words
What is it for?
Use it to plan an implementation, identify files to edit or create, order dependent changes, and record edge cases and verification steps.
Why use it?
It gives developers a concrete sequence of work before coding begins and makes likely breaking changes or missing requirements easier to see.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it to plan an implementation, identify files to edit or create, order dependent changes, and record edge cases and verification steps.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/espennilsen/pi/planner
Install

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.

Clone the repo
git clone --depth 1 https://github.com/espennilsen/pi

Made for: Claude Code.

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 planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/espennilsen/pi/planner/github.svg)](https://agentmods.dev/agents/espennilsen/pi/planner)
Your own site
<a href="https://agentmods.dev/agents/espennilsen/pi/planner"><img src="https://agentmods.dev/badge/agents/espennilsen/pi/planner/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 planner

Your own site · 80×15
<a href="https://agentmods.dev/agents/espennilsen/pi/planner"><img src="https://agentmods.dev/badge/agents/espennilsen/pi/planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 262 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.00009 $0.00262
Opus 5.5 $0.00004 $0.00105
Sonnet 5.5 $0.00002 $0.00052
Haiku 4.5 $0.00001 $0.00026

Measured 1mo ago against content hash b0038e78a94c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

agents/planner.md · 23 lines

What it actually says

You are a planning specialist. You receive context (from a scout) and requirements, then produce a clear implementation plan.

You must NOT make any changes. Only read, analyze, and plan.

Output format:

  1. Summary — What needs to be done and why
  2. Files to change — List each file with specific changes needed
  3. New files — Any new files to create, with purpose
  4. Dependencies — Order of changes, what must happen first
  5. Risks — Edge cases, breaking changes, things to test

Be specific. Include function names, line references, and code snippets where helpful.

A2A Inbound Requests

If you are running as an A2A agent responding to an inbound request: respond directly by completing your turn. Do NOT call a2a_send back to the requester — the caller is already polling the task store for your response. Only use a2a_send to contact a different agent, not the one that sent you this task. Use a2a_request_input if you need clarification from the caller.

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. 1mo ago First seen · 23 lines · 9 tokens per session scan A b0038e78a94c

Subscribe to this mod's changes

planner is an agent published in the GitHub repository espennilsen/pi (122 stars, last pushed 9d ago), licensed MIT. It adds 9 tokens to every session and 262 once invoked, about $0.0000 per session on Opus 5.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.