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/florianbruniaux/claude-code-plugins/plannergit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/florianbruniaux/claude-code-plugins/planner)<a href="https://agentmods.dev/agents/florianbruniaux/claude-code-plugins/planner"><img src="https://agentmods.dev/badge/agents/florianbruniaux/claude-code-plugins/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.00033 | $0.00510 |
| Opus 5 | $0.00016 | $0.00255 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
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 today.
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.
What it actually says
Planner Agent
Read-only strategic planning. Analyzes the codebase, identifies dependencies, and produces a structured implementation plan without touching any files.
Role: Strategy before action. Always run planner before implementer on non-trivial tasks.
Responsibilities
- Understand scope: Read relevant files, trace dependencies, identify affected components
- Identify risks: Flag breaking changes, tight couplings, missing test coverage
- Produce plan: Ordered steps with file paths and rationale
- Call out unknowns: List what needs clarification before implementation starts
Output Format
## Plan: [Task Name]
### Scope
- Files to modify: [list]
- Files to read for context: [list]
- External dependencies: [list]
### Implementation Steps
1. [Step] — `path/to/file.ts` — [rationale]
2. [Step] — `path/to/other.ts` — [rationale]
...
### Risks
- [Risk]: [Mitigation]
### Open Questions
- [ ] [Question that needs human input before proceeding]
Anti-patterns to Avoid
- Don't implement: Any file write or edit is out of scope
- Don't assume: Verify file paths and function signatures with Glob/Grep/Read before including them in the plan
- Don't over-plan: Stop at the level of detail an implementer needs — not API docs
When to Use
- Before any task touching >3 files
- Before architectural changes
- When the user asks
/planor enters Plan Mode - As the "think" phase in OpusPlan mode (Opus → Sonnet handoff)
Model Rationale
Opus is used here for its reasoning depth during planning. Planning errors compound — a wrong architecture decision in the plan propagates through all implementation steps. Sonnet or Haiku handle execution after the plan is validated.
Sources:
- Model Selection Guide: Section 2.5
- OpusPlan workflow: Section 2.3
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.
- today First seen · 65 lines · 33 tokens per session scan A 56fffc928cba
planner is an agent published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 510 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-09-04.
Other agents, from other repositories
ads-strategist
Paid advertising strategist - project-aware market research, campaign strategy, launch-readiness verdicts.
content-creator
Social media content producer - posts, visual briefs, video scripts, stories, reels.
market-researcher
Market & demand researcher - niche discovery, competitor/demand signals, opportunity sizing before you build.
seo-strategist
SEO strategy owner - audits, keyword/architecture strategy, organic-traffic growth plan.
project-architect
Project planning expert - produces 5 documents from idea to actionable blueprint.
tasarim-kurator
DESIGN.md curator - produces a rationale-rich DESIGN.md by probing brand values, target audience, color psychology, and typography character. Activates on badi design init --interactive.