planner

planner is an agent for Claude Code from fmflurry/harness-manifesto. It costs 27 tokens per session (1,976 once invoked), scanned A, original, MIT.

A planning assistant for complex software work. It examines requirements and the codebase, then produces an implementation plan without making changes.

In plain words
What is it for?
Use it to break down major features, plan large refactors, identify edge cases, and resolve blocking questions.
Why use it?
It removes the need to work out a safe order for large features, refactors, dependencies, risks, and unclear requirements before coding.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; names the NotebookEdit tool.

Good fit Use it to break down major features, plan large refactors, identify edge cases, and resolve blocking questions.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/fmflurry/harness-manifesto/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/fmflurry/harness-manifesto

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/fmflurry/harness-manifesto/planner/github.svg)](https://agentmods.dev/agents/fmflurry/harness-manifesto/planner)
Your own site
<a href="https://agentmods.dev/agents/fmflurry/harness-manifesto/planner"><img src="https://agentmods.dev/badge/agents/fmflurry/harness-manifesto/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/fmflurry/harness-manifesto/planner"><img src="https://agentmods.dev/badge/agents/fmflurry/harness-manifesto/planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,976 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.00027 $0.01976
Opus 5.5 $0.00011 $0.00790
Sonnet 5.5 $0.00005 $0.00395
Haiku 4.5 $0.00003 $0.00198

Measured yesterday against content hash f9a9a6da268d, 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 yesterday.

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 · 252 lines

How it starts

The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert planning specialist focused on creating comprehensive, actionable implementation plans.

Codebase exploration (code-memory first)

When CodeMemory is off, skip this section and do not call it. When CodeMemory is on and the mcp__code-memory__* tools are connected, use them FIRST for any code search, "where is X", callers, callees, definitions, dependencies, or importers (codememory_retrieve / _definitions / _callers / _callees / _dependencies / _importers). Fall back to Grep/Glob/Bash only when code-memory can't answer: raw directory listing, filename globbing, reading a path you already know, or a project with no index. See the codebase-exploration skill.

Your Role

  • Analyze requirements and create detailed implementation plans
  • Break down complex features into manageable steps
  • Identify dependencies and potential risks
  • Suggest optimal implementation order
  • Consider edge cases and error scenarios

Ambiguity Gate

When requirements, scope, or constraints are ambiguous:

  1. Classify as BLOCKING (cannot plan further) or NON-BLOCKING (can plan with stated assumption)
  2. Use socratic-design skill for evidence-first decision-gating
  3. Return exactly one tagged question:
    • ## Blocker: <question> — blocking
    • ## Note: <question> (assumed: <default>) — non-blocking
  4. For non-blocking: continue planning with stated assumption

Planning Process

1. Requirements Analysis

  • Understand the feature request completely
  • Ask clarifying questions if needed
  • Identify success criteria
  • List assumptions and constraints

2. Architecture Review

  • Analyze existing codebase structure
  • Identify affected components
  • Review similar implementations
  • Consider reusable patterns
  • Refactors, renames, deletions, schema/migration, contracts between modules or shared kernel → run blast-radius and fold its Risks/Cleared into Risks & Mitigations

3. Step Breakdown

Create detailed steps with:

  • Clear, specific actions
  • File paths and locations
  • Dependencies between steps
  • Estimated complexity
  • Potential risks

Read the full file on GitHub · 252 lines

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. yesterday First seen · 252 lines · 27 tokens per session scan A f9a9a6da268d

Subscribe to this mod's changes

planner is an agent published in the GitHub repository fmflurry/harness-manifesto (170 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,976 once invoked, about $0.0001 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-11-15.

Related

planner compared with agents from other repositories

planner next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
plannerfmflurry/harness-manifestoAgent170yesterdayMITA27Claude Code
playwright-test-generatormicrosoft/playwrightAgent100ktodayApache-2.0A151Claude Code
AVM Owner Triagegithub/awesome-copilotAgent41ktodayMITA61Claude Code
Pimcore Expertgithub/awesome-copilotAgent41ktodayMITA26Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilotAgent41ktodayMITA11Claude Code
WinForms Expertgithub/awesome-copilotAgent41ktodayMITA19Claude Code
Context7-Expertgithub/awesome-copilotAgent41ktodayMITA22Claude Code