A planning command that requires a written development plan before code is changed. It uses separate reviews for the approach and system design, then lists tasks, risks, and checks.

Use it to plan a feature, fix, or larger code change before development. It helps define the architecture, split work into tasks, estimate task size, and describe how the result will be verified.

It reduces the chance of starting with unclear requirements or a design that later needs major rework. It also makes dependencies and risks visible before implementation begins.

plan — Command for Claude Code by liortesta/ClawdAgent

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/liortesta/ClawdAgent

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/commands/liortesta/clawdagent/plan/github.svg)](https://agentmods.dev/commands/liortesta/clawdagent/plan)

Your own site

<a href="https://agentmods.dev/commands/liortesta/clawdagent/plan"><img src="https://agentmods.dev/badge/commands/liortesta/clawdagent/plan/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/commands/liortesta/clawdagent/plan"><img src="https://agentmods.dev/badge/commands/liortesta/clawdagent/plan.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 357 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.00000	$0.00357
Opus 5.5	$0.00000	$0.00143
Sonnet 5.5	$0.00000	$0.00071
Haiku 4.5	$0.00000	$0.00036

Measured 1mo ago against content hash 48ee004a48b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan 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.

.claude/commands/plan.md · 49 lines

What it actually says

Strategic Planning

Before writing ANY code, create a detailed plan with multi-agent input.

Process:

Understand: Read the requirement carefully. Ask clarifying questions if anything is ambiguous.
CTO Review: Use the CTO agent to evaluate the overall approach — is this the right direction?
Architecture Design: Use the architect agent to design the solution — modules, interfaces, data model
Break Down: Split into tasks with clear dependencies
Estimate Complexity: Rate each task (S/M/L/XL)
Risk Assessment: Identify risks and mitigation strategies
Present Plan: Show the complete plan for user approval

Plan Template:

## Plan: [Feature/Task Name]

### Goal
[1-2 sentences: what we're building and why]

### Approach
[CTO-approved approach with rationale]

### Architecture
[Architect-designed structure]

### Tasks
| # | Task | Size | Depends On | Files |
|---|------|------|-----------|-------|
| 1 | ... | S | - | file1.ts |
| 2 | ... | M | 1 | file2.ts, file3.ts |

### Risks
- [Risk 1]: [Mitigation]
- [Risk 2]: [Mitigation]

### Verification
- [ ] [How to verify task 1]
- [ ] [How to verify task 2]
- [ ] [Final integration test]

Rules:

NEVER start coding before the plan is approved
ALWAYS get CTO input for tasks touching >5 files
ALWAYS include verification steps — "how do we know it works?"

$ARGUMENTS

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.

1mo ago First seen · 49 lines · 0 tokens per session scan A 48ee004a48b8

Subscribe to this mod's changes

plan is a command published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 357 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-08-30.

Planning

plan

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Strategic Planning

Process:

Plan Template:

Rules:

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement