planner

A planning assistant that writes product requirements documents, implementation plans, and technical specifications. It records architectural decisions before coding begins.

In plain words
What is it for?
Use it to describe a feature, plan its implementation, create a specification, and document the architecture and decisions behind it.
Why use it?
It turns an unclear feature request into a written plan that can be reviewed before implementation. This helps prevent coding from starting without agreed requirements or design choices.

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/ecodelearn/template-claude-code-ts/planner
Clone the repo
git clone --depth 1 https://github.com/ecodelearn/template-claude-code-ts

Made for: Claude Code.

Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 650 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00046 $0.00650
Opus 5 $0.00023 $0.00325
Sonnet 5 $0.00009 $0.00130
Haiku 4.5 $0.00005 $0.00065

Measured yesterday against content hash f56e38828833, 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 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 · 70 lines

The source is not reproduced here

Licensed WTFPL

The repository is licensed WTFPL, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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 · 70 lines · 46 tokens per session scan A f56e38828833

Subscribe to this mod's changes

planner is an agent published in the GitHub repository ecodelearn/template-claude-code-ts (1 stars, last pushed 1mo ago), licensed WTFPL. It adds 46 tokens to every session and 650 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.

Related

Other agents, from other repositories

hlasm-assembler-specialist

IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…

josstei/maestro-orchestrate · 306 tokens

cloud_architect

Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…

josstei/maestro-orchestrate · 83 tokens

wtfp-research-synthesizer

Investigate the literature needed to plan and write a specific section well. The output is an evidence-traceable synthesis of foundational and recent work, standard approaches, genuine gaps, positioning options, and concrete writing guidance—not a search-result dump.

akougkas/wtf-p · 57 tokens

continuity-checker

Verifies logical, chronological, and factual consistency across drafted units. Flags contradictions, timeline issues, and character state drift.

hannsxpeter/scriveno · 29 tokens

AGENTS

Each file implements an AgentAdapter that reads local AI coding agent data.

eat-pray-ai/wingman · 0 tokens

observer

Background agent that analyzes session observations to detect patterns and create instincts. Uses Haiku for cost-efficiency. v2.1 adds project-scoped instincts.

x-cmd/skill · 33 tokens