automagik-cli: Command for Claude Code

.claude/commands/planner.md

planner is a command for Claude Code from namastexlabs/automagik-cli. It costs 0 tokens per session (1,690 once invoked), scanned A, original, MIT.

An interactive planning command for exploring and revising a step-by-step plan for a complex task.

In plain words
What is it for?
It helps plan new features, large refactors, architecture changes, and investigations such as finding a memory leak.
Why use it?
It helps resolve unclear requirements and compare approaches before implementation begins.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is namastexlabs/automagik-cli's own configuration. It tells Claude Code how to work on automagik-cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything automagik-cli configures →

Reuse

Borrowing it

Nothing to install: this file belongs to namastexlabs/automagik-cli. 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/namastexlabs/automagik-cli/main/.claude/commands/planner.md
Clone the repo
git clone --depth 1 https://github.com/namastexlabs/automagik-cli

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/commands/namastexlabs/automagik-cli/planner.svg)](https://agentmods.dev/commands/namastexlabs/automagik-cli/planner)
Your own site
<a href="https://agentmods.dev/commands/namastexlabs/automagik-cli/planner"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-cli/planner.svg" alt="Measured on agentmods" 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,690 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.01690
Opus 5 $0.00000 $0.00845
Sonnet 5 $0.00000 $0.00338
Haiku 4.5 $0.00000 $0.00169

Measured 3d ago against content hash 4059eacbcbbb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 3d 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/commands/planner.md · 267 lines

How it starts

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

/planner


allowed-tools: mcp__zen__planner(), Read(), Write(), Bash(), Glob(), mcp__zen__docgen(), mcp__wait__wait_minutes(*) description: Interactive step-by-step planning for complex tasks with branching and revision capabilities

Transform vague requirements into concrete, actionable plans through iterative refinement and exploration of alternatives.

The Power of Interactive Planning

Unlike static planning, the Zen planner enables:

  • Step-by-Step Thinking: Build plans incrementally with deep reflection
  • Branching Exploration: Try different approaches without losing progress
  • Dynamic Revision: Update earlier steps as understanding deepens
  • Forced Reflection: Complex plans (≥5 steps) trigger deep thinking pauses
  • Context Persistence: Plans survive across sessions via continuation IDs

Usage Examples

# Plan a new feature
/planner "Add real-time collaboration to agent system"

# Plan a complex refactoring
/planner "Refactor routing logic to support dynamic agent registration"

# Plan an investigation
/planner "Investigate and fix memory leak in long-running sessions"

# Plan with specific model
/planner "Design microservices architecture" model="gemini"

How It Works

Planning Flow

graph TD
    A[Initial Request] --> B[Step 1: High-level understanding]
    B --> C[Step 2: Break down components]
    C --> D[Step 3: Identify dependencies]
    D --> E{Need alternatives?}
    E -->|Yes| F[Branch: Explore approach B]
    E -->|No| G[Step 4: Detail implementation]
    F --> G
    G --> H[Step 5: Risk assessment]
    H --> I{Revisions needed?}
    I -->|Yes| J[Revise earlier steps]
    I -->|No| K[Final plan ready]
    J --> K

Deep Thinking Enforcement

For complex plans (≥5 steps), the first 3 steps enforce thinking pauses:

  • Prevents surface-level planning
  • Ensures thorough consideration of alternatives
  • Identifies hidden dependencies early
  • Avoids tactical details before strategic decisions

Read the full file on GitHub · 267 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. 3d ago First seen · 267 lines · 0 tokens per session scan A 4059eacbcbbb

Subscribe to this mod's changes

planner is a command published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,690 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-04.