plan

plan is a command for coding agents from CloudAI-X/claude-workflow-v2. It costs 21 tokens per session (957 once invoked), scanned A, original, MIT.

A command-based workflow for creating and maintaining a PLAN.md file, a project plan stored in the repository.

In plain words
What is it for?
It helps create a plan for a new task, show current status, update phases, preserve completed items, and mark the project finished.
Why use it?
It keeps tasks, progress, open questions, and blockers visible across work sessions.

Command

Part of the claude-workflow-v2 plugin — 14 skills, 26 commands, 7 agents, 6 hooks shipped together

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 commands/cloudai-x/claude-workflow-v2/plan
Clone the repo
git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2

Or install claude-workflow-v2, the plugin that ships this one along with the rest of its 14 skills, 26 commands, 7 agents, 6 hooks.

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 plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/cloudai-x/claude-workflow-v2/plan.svg)](https://agentmods.dev/commands/cloudai-x/claude-workflow-v2/plan)
Your own site
<a href="https://agentmods.dev/commands/cloudai-x/claude-workflow-v2/plan"><img src="https://agentmods.dev/badge/commands/cloudai-x/claude-workflow-v2/plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 957 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.00021 $0.00957
Opus 5 $0.00010 $0.00478
Sonnet 5 $0.00004 $0.00191
Haiku 4.5 $0.00002 $0.00096

Measured 4d ago against content hash 6b8007f01085, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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.

commands/plan.md · 126 lines

How it starts

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

Persistent Planning

Create, update, and track a structured project plan in PLAN.md.

Context

  • Existing plan: !cat PLAN.md 2>/dev/null | head -50 || echo "No PLAN.md found"
  • Project structure: !ls -la 2>/dev/null | head -20
  • Current branch: !git branch --show-current
  • Recent commits: !git log --oneline -5 2>/dev/null || echo "No commits"

Behavior Based on Arguments

Interpret $ARGUMENTS to determine the action:

If $ARGUMENTS is "status" or "show":

  • Read PLAN.md and display current progress
  • Show completion percentage for each phase
  • Highlight the next actionable task
  • List any open questions or blockers

If $ARGUMENTS is "complete" or "done":

  • Update the current phase to "done"
  • If all phases are done, add a completion timestamp
  • Summarize what was accomplished

If PLAN.md already exists and $ARGUMENTS is a new task/description:

  • Read the existing plan
  • Add the new task(s) to the appropriate phase
  • Preserve all existing progress (checked items stay checked)
  • Update the plan status

If PLAN.md does NOT exist:

  • Create a new PLAN.md with the structure below
  • Populate based on $ARGUMENTS description
  • Set phase to "planning"

PLAN.md Structure

When creating or updating PLAN.md, use this exact structure:

# Project Plan

> Status: **[planning | implementing | verifying | done]**
> Created: [date]
> Last Updated: [date]

## Objective

[Clear, concise statement of what this plan achieves]

## Tasks

### Phase 1: [Phase Name]

- [ ] Task 1.1 — [description]
  - Depends on: [nothing | task X.Y]
- [ ] Task 1.2 — [description]
  - Depends on: Task 1.1
- [x] Task 1.3 — [completed task description]
  - Depends on: nothing
  - Completed: [date]

### Phase 2: [Phase Name]

- [ ] Task 2.1 — [description]
  - Depends on: Phase 1
- [ ] Task 2.2 — [description]
  - Depends on: Task 2.1

### Phase 3: Verification

- [ ] Run all tests
- [ ] Review changes
- [ ] Update documentation

## Architecture Decisions

| Decision   | Options Considered   | Chosen   | Rationale |
| ---------- | -------------------- | -------- | --------- |
| [decision] | [option A, option B] | [chosen] | [why]     |

## Open Questions

- [ ] [Question 1 — what needs to be answered]
- [x] [Question 2 — answered: [answer]]

## Progress Log

| Date   | Update          |
| ------ | --------------- |
| [date] | [what was done] |

Read the full file on GitHub · 126 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. 4d ago First seen · 126 lines · 0 tokens per session scan A 6b8007f01085

Subscribe to this mod's changes

plan is a command published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,413 stars, last pushed 9d ago), licensed MIT. It adds 21 tokens to every session and 957 once invoked, about $0.0001 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.