plan

plan is a command for Claude Code from znlnzi/claude-config-studio. It costs 11 tokens per session (398 once invoked), scanned A, original, MIT.

A command that creates a structured implementation plan before code is written.

In plain words
What is it for?
Use it for new features, architecture changes, complex refactoring, or work spanning several files; code is held back until the plan is confirmed.
Why use it?
It exposes unclear requirements, technical risks, dependencies, affected areas, and verification steps before changes begin.

Command for Claude Code

Written for Claude Code: installed under .claude/.

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/znlnzi/claude-config-studio/plan
Clone the repo
git clone --depth 1 https://github.com/znlnzi/claude-config-studio

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 plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/znlnzi/claude-config-studio/plan.svg)](https://agentmods.dev/commands/znlnzi/claude-config-studio/plan)
Your own site
<a href="https://agentmods.dev/commands/znlnzi/claude-config-studio/plan"><img src="https://agentmods.dev/badge/commands/znlnzi/claude-config-studio/plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 398 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.1 $0.00011 $0.00398
Opus 5 $0.00005 $0.00199
Sonnet 5 $0.00002 $0.00080
Haiku 4.5 $0.00001 $0.00040

Measured 5d ago against content hash 1bbdfb794a95, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, 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 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.

.claude/commands/plan.md · 70 lines

What it actually says

/plan - 实现规划

在开始编码之前,创建一个结构化的实现计划。

工作流

1. 需求澄清

  • 确认你理解了要构建什么
  • 列出已知需求和假设
  • 标记需要确认的问题

2. 风险评估

  • 识别潜在的技术障碍
  • 评估对现有功能的影响
  • 列出外部依赖

3. 阶段拆解

将工作分解为 3-5 个可管理的阶段:

  • 每个阶段都应该可以独立验证
  • 标明阶段间的依赖关系
  • 估算每个阶段的工作量

4. 计划确认

在获得用户明确确认之前,不要生成任何代码。

计划模板

## 实现计划: [功能名称]

### 概述
[一句话描述]

### 需求
- [ ] 需求 1
- [ ] 需求 2

### 架构变更
- [描述需要的架构修改]

### 实现阶段

#### 阶段 1: [名称]
- 修改文件: [列表]
- 关键变更: [描述]
- 验证方法: [如何验证]

#### 阶段 2: [名称]
...

### 测试策略
- 单元测试: [范围]
- 集成测试: [范围]

### 风险
- 风险 1: [描述] → 缓解: [方案]

何时使用

  • 新功能开发
  • 架构变更
  • 复杂重构
  • 多文件修改
  • 需求不明确时
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 · 70 lines · 11 tokens per session scan A 1bbdfb794a95

Subscribe to this mod's changes

plan is a command published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 398 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-31.