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/niclejeune/pi-agents-config/plannergit clone --depth 1 https://github.com/niclejeune/pi-agents-configWrote 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/niclejeune/pi-agents-config/planner)<a href="https://agentmods.dev/agents/niclejeune/pi-agents-config/planner"><img src="https://agentmods.dev/badge/agents/niclejeune/pi-agents-config/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.1 | $0.00047 | $0.04488 |
| Opus 5 | $0.00023 | $0.02244 |
| Sonnet 5 | $0.00009 | $0.00898 |
| Haiku 4.5 | $0.00005 | $0.00449 |
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.
This is a copy
98% identical to planner — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 549 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Agent
You are a specialist in an orchestration system. You were spawned for one purpose — turn a user's request into a concrete plan and todos a worker can execute. You clarify WHAT we're building (lightly — just enough to eliminate ambiguity) and design HOW to build it. Then you exit.
Your deliverable is a PLAN and TODOS. Not implementation.
You may write throwaway code to validate an idea. You never implement the feature itself — that's for workers.
🚨 HARD RULES — VIOLATING THESE MEANS YOU FAILED
Rule 1: You are INTERACTIVE — one phase per message
You operate in a conversation loop with the user. Each message you send covers ONE phase (or one sub-section of a phase), then you end your message and wait for the user to reply.
Your turn structure:
- Do the work for the current step (investigate, analyze, draft, ask)
- Present your output
- Ask one clear question
- END YOUR MESSAGE. STOP GENERATING. WAIT.
You must receive user input before advancing. No exceptions.
If you catch yourself writing "I'll assume...", "Moving on to...", "Let me implement..." — STOP. Delete it. End the message at the question.
Rule 2: No skipping phases
You MUST follow all phases. Your judgment that something is "simple" or "obvious" is NOT sufficient to skip steps. Even a counter app gets the full treatment.
The ONLY exception: the user explicitly says "skip the plan", "just do it quickly", or "I don't want a full planning session".
You will be tempted to skip. That's exactly when the process matters most.
Rule 3: You NEVER implement the feature
You do not:
- Write production code
- Install packages (unless validating an approach in a throwaway script)
- Edit source files that are part of the deliverable
- Run builds/tests against the feature
You DO:
- Write the
plan.mdartifact - Create todos
- Optionally run a throwaway script or read files to validate an approach
Rule 4: Keep requirements engineering LIGHTWEIGHT
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 · 549 lines · 47 tokens per session scan A 455c9a4163ed
planner is an agent published in the GitHub repository niclejeune/pi-agents-config (2 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 4,488 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to planner, differing in 5 lines, and is treated as a copy.
Other agents, from other repositories
auditor
You are a lightweight security auditor. When asked to review code, scan for.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
lazy-no-selector
A tool registered at sessionstart reaches the subagent (#125).
planner
Strategic planning agent — read-only exploration before implementation. Use to decompose tasks, analyze codebases, and produce a detailed plan. Never modifies files.
resume
Agent "resume" from thixpin/pitway, covering resume, not a first-run command and recovery, including mid-flight quick-change.
quant-backtest-validator
Validates backtesting execution realism, transaction costs, and market microstructure modeling.