planning

planning is a skill for Claude Code, Codex from davila7/claude-code-templates. It costs 59 tokens per session (712 once invoked), scanned A, original, MIT.

A system for keeping a structured task plan in Markdown files, which are plain-text documents commonly used for notes and project documentation. It tracks goals, research findings, decisions, errors, and progress across complex tasks.

In plain words
What is it for?
Use it to create plans, record discoveries, track decisions and errors, and log progress during long tasks or research projects.
Why use it?
It keeps multi-step work organized when a task spans research, design, implementation, and testing. The saved files preserve context between sessions.

Skill for Claude CodeCodex

About the project

Claude Code Templates is a command-line tool and catalogue for configuring Anthropic’s Claude Code with agents, commands, settings, hooks, integrations, skills, and project templates. Developers use it to browse and install reusable components for their coding workflows. The catalogue includes many of these Claude Code components.

davila7/claude-code-templates · 30,520 stars · on GitHub

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 skills/davila7/claude-code-templates/planning
Any agent
npx skills add davila7/claude-code-templates --skill planning
Clone the repo
git clone --depth 1 https://github.com/davila7/claude-code-templates

Made for: Claude Code, Codex.

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 planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/davila7/claude-code-templates/planning.svg)](https://agentmods.dev/skills/davila7/claude-code-templates/planning)
Your own site
<a href="https://agentmods.dev/skills/davila7/claude-code-templates/planning"><img src="https://agentmods.dev/badge/skills/davila7/claude-code-templates/planning.svg" alt="Measured on agentmods" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 712 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.00059 $0.00712
Opus 5 $0.00030 $0.00356
Sonnet 5 $0.00012 $0.00142
Haiku 4.5 $0.00006 $0.00071

Measured 5d ago against content hash 34a4a12808a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

planning 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 5d 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.

cli-tool/components/skills/ai-maestro/planning/SKILL.md · 84 lines

How it starts

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

AI Maestro Planning

Solve the execution problem -- staying focused during complex, multi-step tasks. Uses persistent markdown files to track goals, findings, and progress so you never lose context. Part of the AI Maestro suite.

When to Use

  • Multi-step tasks (3+ steps)
  • Research projects
  • Building features requiring >5 tool calls
  • Any task where you might lose track of the goal

The 3-File Pattern

Create in docs_dev/ (or $AIMAESTRO_PLANNING_DIR):

File Purpose Update When
task_plan.md Goals, phases, decisions, errors After each phase
findings.md Research, discoveries, resources During research
progress.md Session log, test results Throughout session

Quick Start

PLAN_DIR="${AIMAESTRO_PLANNING_DIR:-docs_dev}"
mkdir -p "$PLAN_DIR"

Then create task_plan.md with:

# Task: [Goal]

## Phases
- [ ] Phase 1: Research
- [ ] Phase 2: Design
- [ ] Phase 3: Implement
- [ ] Phase 4: Test

## Decisions
| Decision | Rationale | Date |
|----------|-----------|------|

## Errors Encountered
| Error | Attempt | Resolution |
|-------|---------|------------|

The 6 Rules

  1. Create plan first -- Never start complex work without task_plan.md
  2. Read before decide -- Re-read the plan before any major decision
  3. Update after act -- Mark phases complete, log what changed
  4. 2-action rule -- After every 2 search/browse operations, save findings to findings.md
  5. Log all errors -- Every error goes in the plan with attempt number and resolution
  6. Never repeat failures -- If an action failed, change your approach

The 3-Strike Protocol

Strike Action
1 Diagnose root cause, apply targeted fix
2 Try a different approach entirely
3 Question assumptions, search for similar issues
After 3 Escalate to user with all attempts documented

The 5-Question Reboot

Read the full file on GitHub · 84 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. 5d ago First seen · 84 lines · 59 tokens per session scan A 34a4a12808a0

Subscribe to this mod's changes

planning is a skill published in the GitHub repository davila7/claude-code-templates (30,520 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 712 once invoked, about $0.0003 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.