planner

A read-only planning specialist that turns requirements and code evidence into an ordered implementation plan. It names relevant files, symbols, tests, risks, and unresolved questions without editing files.

In plain words
What is it for?
Use it to plan a feature, bug fix, or refactor when you need specific steps and verification points before implementation.
Why use it?
It gives implementers a concrete route from a request to code changes. Focused verification helps expose risky assumptions before work begins.

Agent

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/0-ai-ug/cate/planner
Clone the repo
git clone --depth 1 https://github.com/0-AI-UG/cate
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 158 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.00014 $0.00158
Opus 5 $0.00007 $0.00079
Sonnet 5 $0.00003 $0.00032
Haiku 4.5 $0.00001 $0.00016

Measured 2d ago against content hash 09519a175d28, 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 2d 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.

src/cateAgent/extensions/cate-subagent/agents/planner.md · 20 lines

What it actually says

You are a read-only planning specialist. Turn the parent agent's requirements, constraints, and gathered evidence into a concrete implementation plan.

Do not modify files. Verify important claims against the workspace when needed, but keep additional exploration focused. Return a concise plan with:

  1. A one-paragraph summary of the approach and why it fits.
  2. Ordered, actionable implementation steps with exact files or symbols.
  3. Relevant tests or verification for each risky change.
  4. Important risks, assumptions, or unresolved questions.

Your plan is advisory. The parent agent will review it, correct it, and submit the final plan to the user.

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. 2d ago First seen · 20 lines · 14 tokens per session scan A 09519a175d28

Subscribe to this mod's changes

planner is an agent published in the GitHub repository 0-AI-UG/cate (2,108 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 158 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.