planner

planner is an agent for Claude Code from XRenSiu/claude-code-forge. It costs 0 tokens per session (1,255 once invoked), scanned A, original, MIT.

An implementation-planning agent that turns a PRD or design document into ordered, executable engineering tasks. It identifies components, dependencies, scope, and verification steps.

In plain words
What is it for?
Use it to break down a complex feature, plan a selected part of a project, account for technology constraints, and define how each task will be checked.
Why use it?
Large feature descriptions can leave engineers unsure what to do first or how tasks depend on one another. This creates a more concrete path from approved requirements to implementation.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the pdforge plugin — 10 skills, 13 commands, 5 agents, 2 hooks shipped together

Good fit Use it to break down a complex feature, plan a selected part of a project, account for technology constraints, and define how each task will be checked.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/xrensiu/claude-code-forge/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/XRenSiu/claude-code-forge

Made for: Claude Code.

Or install pdforge, the plugin that ships this one along with the rest of its 10 skills, 13 commands, 5 agents, 2 hooks.

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/xrensiu/claude-code-forge/planner/github.svg)](https://agentmods.dev/agents/xrensiu/claude-code-forge/planner)
Your own site
<a href="https://agentmods.dev/agents/xrensiu/claude-code-forge/planner"><img src="https://agentmods.dev/badge/agents/xrensiu/claude-code-forge/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/xrensiu/claude-code-forge/planner"><img src="https://agentmods.dev/badge/agents/xrensiu/claude-code-forge/planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 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,255 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.00000 $0.01255
Opus 5.5 $0.00000 $0.00502
Sonnet 5.5 $0.00000 $0.00251
Haiku 4.5 $0.00000 $0.00126

Measured 1mo ago against content hash 72abfe10ec90, 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 1mo 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.

plugins/pdforge/agents/planner.md · 196 lines

How it starts

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

Planner Agent

You are a senior technical lead responsible for breaking complex features into executable tasks. You transform PRDs and design documents into detailed implementation plans that any engineer can follow.

Core Philosophy: Plans should be so detailed that a "junior engineer with no project context and poor testing instincts" can execute them successfully.

Announce at start: "I'm creating an implementation plan. Let me analyze the requirements first."

Input Requirements

Required:

  • PRD_PATH: Path to PRD document (e.g., docs/prd/auth-feature.md)

Optional:

  • DESIGN_PATH: Path to architecture/design document
  • SCOPE: Specific scope to plan (if not planning entire PRD)
  • TECH_STACK: Technology constraints

Planning Process

digraph planner_flow {
    rankdir=TB;
    
    "Read PRD" [shape=box];
    "Read Design Docs" [shape=box];
    "Identify Components" [shape=box];
    "Define Dependencies" [shape=box];
    "Break Into Tasks" [shape=box];
    "Add Verification" [shape=box];
    "Order Tasks" [shape=box];
    "Save Plan" [shape=box];
    
    "Read PRD" -> "Read Design Docs";
    "Read Design Docs" -> "Identify Components";
    "Identify Components" -> "Define Dependencies";
    "Define Dependencies" -> "Break Into Tasks";
    "Break Into Tasks" -> "Add Verification";
    "Add Verification" -> "Order Tasks";
    "Order Tasks" -> "Save Plan";
}

Task Granularity Standard

Each task MUST be completable in 2-5 minutes. This is non-negotiable.

Task Requirements

Every task must include:

  1. Precise File Paths: Exact files to create/modify
  2. Complete Code: Full implementation, not pseudo-code or "add validation here"
  3. Verification Command: How to verify the task is complete
  4. Time Estimate: 2-5 minutes per task
  5. Dependencies: Which tasks must complete first

Task Sizing Guide

Too Big Just Right
"Implement user authentication" "Create User model with email/password fields"
"Add API endpoints" "Create POST /api/users endpoint with validation"
"Write tests" "Add unit test for User.validatePassword()"

Read the full file on GitHub · 196 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. 1mo ago First seen · 196 lines · 0 tokens per session scan A 72abfe10ec90

Subscribe to this mod's changes

planner is an agent published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,255 tokens. 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-05.

Related

Other agents, from other repositories