LegendaryTeam_For_Claude: Command for Claude Code

.claude/commands/plan.md

plan is a command for Claude Code from RegardV/LegendaryTeam_For_Claude. It costs 0 tokens per session (3,730 once invoked), scanned A, original, MIT.

A command that creates a step-by-step implementation plan before coding. It reviews the requested change, the existing code, dependencies, risks, and suggested design.

In plain words
What is it for?
Use it to plan features, refactors, architecture changes, and detailed work such as authentication, shopping carts, or real-time notifications.
Why use it?
It turns a broad coding request into a concrete checklist and exposes blockers or trade-offs before implementation begins.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is RegardV/LegendaryTeam_For_Claude's own configuration. It tells Claude Code how to work on LegendaryTeam_For_Claude 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 LegendaryTeam_For_Claude configures →

Reuse

Borrowing it

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

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/regardv/legendaryteam_for_claude/plan/github.svg)](https://agentmods.dev/commands/regardv/legendaryteam_for_claude/plan)
Your own site
<a href="https://agentmods.dev/commands/regardv/legendaryteam_for_claude/plan"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/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.

agentmods 80×15 button for plan

Your own site · 80×15
<a href="https://agentmods.dev/commands/regardv/legendaryteam_for_claude/plan"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/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 3,730 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.03730
Opus 5 $0.00000 $0.01865
Sonnet 5 $0.00000 $0.00746
Haiku 4.5 $0.00000 $0.00373

Measured 9d ago against content hash 937542b9adf9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 9d 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 · 654 lines

How it starts

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

/plan - Implementation Planning & Strategy

Create detailed implementation plans before coding, ensuring clear strategy and preventing over-engineering.


Usage

# Create implementation plan for a feature
/plan "Add user authentication with OAuth2"

# Plan with specific requirements
/plan "Build shopping cart" --requirements "must support multiple currencies, inventory tracking"

# Plan refactoring
/plan refactor "migrate from Redux to Zustand"

# Plan architecture change
/plan architecture "add microservices for payment processing"

# Generate step-by-step plan
/plan "implement real-time notifications" --detailed

What This Command Does

  1. Analyzes the requested feature or change
  2. Breaks down into concrete, actionable steps
  3. Identifies dependencies and blockers
  4. Estimates effort and complexity
  5. Suggests architecture and approach
  6. Creates task checklist
  7. Highlights risks and trade-offs

Command Flow

Step 1: Understand requirement
  → Parse user request
  → Identify scope and goals
  → Clarify any ambiguities

Step 2: Analyze current state
  → Review existing code
  → Identify what exists
  → Find integration points

Step 3: Design approach
  → Choose architecture pattern
  → Select technologies
  → Define data models

Step 4: Break into tasks
  → Create step-by-step plan
  → Identify dependencies
  → Estimate complexity

Step 5: Highlight considerations
  → Security implications
  → Performance impacts
  → Testing requirements
  → Deployment needs

Step 6: Create actionable output
  → Task checklist
  → File locations
  → Code structure

Invokes Agent

@ArchitectureAgent will handle this command with the following context:

Task: Create implementation plan
Feature: ${user_input}
Requirements: ${requirements}

Deliverables:
1. High-level approach and architecture
2. Step-by-step implementation plan
3. File structure and organization
4. Dependencies and integration points
5. Testing strategy
6. Security considerations
7. Performance implications
8. Deployment requirements
9. Estimated effort
10. Risk assessment

Output Format:
- Executive summary
- Detailed step-by-step plan
- Task checklist
- Code structure
- Trade-offs and decisions

Read the full file on GitHub · 654 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. 9d ago First seen · 654 lines · 0 tokens per session scan A 937542b9adf9

Subscribe to this mod's changes

plan is a command published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,730 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.