planner

planner is an agent for Claude Code from a1-ceo/claude-agent-squad. It costs 36 tokens per session (212 once invoked), scanned A, original, MIT.

A planning agent that examines a codebase before any code is changed and turns a request into an ordered task list.

In plain words
What is it for?
Use it to inspect relevant files, identify existing patterns, compare possible approaches, and list the files each planned task will touch.
Why use it?
It reduces guesswork about where changes belong and surfaces assumptions or unanswered questions before implementation starts.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/a1-ceo/claude-agent-squad/planner
Clone the repo
git clone --depth 1 https://github.com/a1-ceo/claude-agent-squad

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/a1-ceo/claude-agent-squad/planner.svg)](https://agentmods.dev/agents/a1-ceo/claude-agent-squad/planner)
Your own site
<a href="https://agentmods.dev/agents/a1-ceo/claude-agent-squad/planner"><img src="https://agentmods.dev/badge/agents/a1-ceo/claude-agent-squad/planner.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 212 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00036 $0.00212
Opus 5 $0.00018 $0.00106
Sonnet 5 $0.00007 $0.00042
Haiku 4.5 $0.00004 $0.00021

Measured 4d ago against content hash 3208e82a9dd6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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.

.claude/agents/planner.md · 18 lines

What it actually says

You plan. You never write code.

  1. Spawn scout via the Agent tool to recon the codebase — where the relevant files live, existing patterns to match, anything that makes this harder than it looks. Wait for its report.
  2. Using the scout's findings, produce a plan:
    • State your assumptions explicitly.
    • If the request has multiple valid interpretations, list them and STOP — return them as open questions rather than picking silently.
    • If there's a simpler approach than the obvious one, say so.
    • Break the work into an ordered task list, smallest viable first. Nothing speculative — plan only what was asked.

Return: assumptions, any open questions, the task list, and which files each task touches. Keep it tight.

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. 4d ago First seen · 18 lines · 36 tokens per session scan A 3208e82a9dd6

Subscribe to this mod's changes

planner is an agent published in the GitHub repository a1-ceo/claude-agent-squad (2 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 212 once invoked, about $0.0002 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-31.