A command that opens the current large project plan for interactive editing. The plan lists the project's goal, execution settings, target branch, and features.

Use it to add, remove, or modify features in an existing mega-plan.

It makes it easier to adjust a multi-feature plan before its implementation starts.

mega-edit — Command by Taoidle

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/taoidle/plan-cascade/mega-edit

Clone the repo

git clone --depth 1 https://github.com/Taoidle/plan-cascade

Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 920 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.

Model	Per session	Once invoked
Fable 5	$0.00024	$0.00920
Opus 5	$0.00012	$0.00460
Sonnet 5	$0.00005	$0.00184
Haiku 4.5	$0.00002	$0.00092

Measured 2d ago against content hash aef04c52ab8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mega-edit 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 2d 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/mega-edit.md · 158 lines

How it starts

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

Edit Mega Plan

Edit the mega-plan.json file interactively to add, remove, or modify features.

Path Storage Modes

Mega-plan file location depends on the storage mode:

New Mode: ~/.plan-cascade/<project-id>/mega-plan.json
Legacy Mode: mega-plan.json in project root

The command uses PathResolver to find the correct file location.

Step 1: Verify Mega Plan Exists

# Get mega-plan path from PathResolver
MEGA_PLAN_PATH=$(uv run python -c "from plan_cascade.state.path_resolver import PathResolver; from pathlib import Path; print(PathResolver(Path.cwd()).get_mega_plan_path())" 2>/dev/null || echo "mega-plan.json")

if [ ! -f "$MEGA_PLAN_PATH" ]; then
    echo "No mega-plan.json found at: $MEGA_PLAN_PATH"
    echo "Use /plan-cascade:mega-plan <description> to create one first."
    exit 1
fi

Step 2: Read Current Plan

Read and parse mega-plan.json:

cat "$MEGA_PLAN_PATH"

Step 3: Display Current Structure

============================================================
CURRENT MEGA PLAN
============================================================

Goal: <goal>
Execution Mode: <mode>
Target Branch: <branch>

Features:
  1. [feature-001] <title>
     - Name: <name>
     - Priority: <priority>
     - Status: <status>
     - Dependencies: <deps or "none">

  2. [feature-002] <title>
     ...

============================================================

Step 4: Ask What to Edit

Use AskUserQuestion to present options:

What would you like to edit?

Options:

Add a new feature - Add another feature to the plan
Remove a feature - Remove an existing feature
Edit a feature - Modify an existing feature's details
Change execution mode - Switch between auto/manual
Change target branch - Modify the merge target

Step 5: Perform the Edit

Option 1: Add a New Feature

Ask for:

Feature name (lowercase-hyphenated, e.g., "feature-analytics")
Title (human readable)
Description (detailed for PRD generation)
Priority (high/medium/low)
Dependencies (comma-separated feature IDs, or "none")

Read the full file on GitHub · 158 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.

2d ago First seen · 158 lines · 24 tokens per session scan A aef04c52ab8f

Subscribe to this mod's changes

mega-edit is a command published in the GitHub repository Taoidle/plan-cascade (124 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 920 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.

Data and AI Git and workflow Multi-Agent Planning claude-code claude-code-plugin developer-tools llm-agents mcp-server

mega-edit

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Edit Mega Plan

Path Storage Modes

Step 1: Verify Mega Plan Exists

Step 2: Read Current Plan

Step 3: Display Current Structure

Step 4: Ask What to Edit

Step 5: Perform the Edit

Option 1: Add a New Feature

What this file has done since we first saw it

Other commands, from other repositories

conv_release

data_cleaning

pypi

local_cluster

webserver

leaderboard