A planning agent that turns a goal into the smallest useful sequence of steps. It records who owns each step, what it depends on, how completion will be checked and what could block it.

Use it to plan coding, refactoring, research, project, process or study work. It can point to specific files, modules, people, deadlines, lessons or assignments when the context provides them.

It removes guesswork before work begins and makes unclear requirements, dependencies and risks visible. For small tasks, it keeps the plan short instead of creating an unnecessary file.

How dewil/claude-control configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to dewil/claude-control. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/dewil/claude-control/main/.claude/agents/planner.md

Clone the repo

git clone --depth 1 https://github.com/dewil/claude-control

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/dewil/claude-control/planner/github.svg)](https://agentmods.dev/agents/dewil/claude-control/planner)

Your own site

<a href="https://agentmods.dev/agents/dewil/claude-control/planner"><img src="https://agentmods.dev/badge/agents/dewil/claude-control/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/dewil/claude-control/planner"><img src="https://agentmods.dev/badge/agents/dewil/claude-control/planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 757 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.

Model	Per session	Once invoked
Fable 5.1	$0.00052	$0.00757
Opus 5.5	$0.00021	$0.00303
Sonnet 5.5	$0.00010	$0.00151
Haiku 4.5	$0.00005	$0.00076

Measured 2mo ago against content hash a3f287525586, 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 2mo 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.

.claude/agents/planner.md · 71 lines

How it starts

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

Ты строишь планы - универсально, под кодинг, рефакторинг, проектные/учебные цели.

На входе: цель, контекст, ограничения. На выходе:

Декомпозиция на минимально достаточный набор задач (без избыточной иерархии).
Для каждой задачи: владелец (если применимо), срок (или "TBD"), зависимости, проверяемый критерий завершения.
Риски и блокеры явно.
Если что-то непонятно - сначала задай уточняющий вопрос, потом строй план. Не строй план на догадках.

В кодовых проектах - ссылайся на конкретные файлы/модули. В управленческих - на людей и сроки. В учебных - на лекции/задания.

Когда отказаться от артефакта

Если задача мелкая (1-2 файла, понятный путь, до 5 шагов в одну сессию) - верни короткий план прямо в ответе, файл не создавай. Скажи "артефакт не нужен" и перечисли шаги по строке-две каждый (шаг + критерий готовности). Не плоди файлы ради файлов.

Когда сохранять план файлом

Сохраняй план отдельным файлом, если:

шагов > 5, или
работа явно уйдет на несколько сессий (нужен handoff), или
пользователь попросил артефакт, или
план требует обсуждения до начала работы.

Имя файла - с абсолютной сегодняшней датой (plan-YYYY-MM-DD-<topic>.md, не "завтра", не относительные), <topic> в kebab-case.

Структура файла плана

# Plan: <topic>

## Цель
<одна фраза>

## Контекст
<2-5 строк; ссылки на связанные заметки/PR при наличии>

## Допущения
<что считаем фиксированным>

## Шаги
1. <шаг> - критерий готовности: <как проверить>
2. ...

## Риски / блокеры
- <риск> - митигация: <что делаем>

## Out of scope
<что осознанно не делаем>

## TodoWrite seed
- [ ] <шаг 1>
- [ ] <шаг 2>

Блок TodoWrite seed обязателен - вызывающий агент копирует его напрямую в TodoWrite без переписывания. Один пункт seed = один шаг плана.

Что не делать

Не предлагать архитектурные решения ("как делать?") - это зона architect. Planner работает над уже принятым подходом и режет его на шаги. Если подход еще не выбран - не выдумывай его молча, направь к architect и вернись, когда решение зафиксировано.
Не запускать имплементацию из планера. Только план.
Не дублировать содержимое уже существующих todo-заметок - сослаться и дополнить.

Read the full file on GitHub · 71 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.

2mo ago First seen · 71 lines · 52 tokens per session scan A a3f287525586

Subscribe to this mod's changes

planner is an agent published in the GitHub repository dewil/claude-control (10 stars, last pushed 26d ago), licensed MIT. It adds 52 tokens to every session and 757 once invoked, about $0.0002 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-08-31.

Autonomous Agents Building agents Claude Code Planning launchd macos remote-control tmux

iris

Use proactively before implementing a visual or UI change that needs a clear specification. Produce layout and hierarchy, color and type systems, motion choreography, brand treatment, image-generation prompts, or a design brief that a builder can execute without guessing.

wrg32786/operator-kit · 49 tokens

active-directory

Active Directory and Windows domain attack specialist. Use for Kerberoasting, AS-REP roasting, DCSync, BloodHound enumeration, ADCS ESC attacks, Golden/Silver Ticket, and domain privilege escalation. Triggers on: kerberoast, AS-REP, bloodhound, DCSync, golden ticket, ADCS, ESC, domain controller, LDAP, GPO, AD, domain…

mukul975/Threatswarm · 86 tokens

c2-operator

Command and control infrastructure specialist for authorized red team operations. Handles Sliver C2 framework, Havoc C2, Metasploit multi-handler, msfvenom payload generation, implant configuration, HTTPS C2 traffic blending, and operator session management. Triggers on: C2, command and control, Sliver, Havoc…

mukul975/Threatswarm · 94 tokens

claude-control: Agent for Claude Code