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.
git clone --depth 1 https://github.com/Taoidle/plan-cascadeWrote 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.
[](https://agentmods.dev/commands/taoidle/plan-cascade/mega-edit)<a href="https://agentmods.dev/commands/taoidle/plan-cascade/mega-edit"><img src="https://agentmods.dev/badge/commands/taoidle/plan-cascade/mega-edit/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.
<a href="https://agentmods.dev/commands/taoidle/plan-cascade/mega-edit"><img src="https://agentmods.dev/badge/commands/taoidle/plan-cascade/mega-edit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00024 | $0.00920 |
| Opus 5.5 | $0.00010 | $0.00368 |
| Sonnet 5.5 | $0.00005 | $0.00184 |
| Haiku 4.5 | $0.00002 | $0.00092 |
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 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.
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.jsonin 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")
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 · 158 lines · 24 tokens per session scan A aef04c52ab8f
mega-edit is a command published in the GitHub repository Taoidle/plan-cascade (133 stars, last pushed 7mo ago), licensed MIT. It adds 24 tokens to every session and 920 once invoked, about $0.0001 per session on Opus 5.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.
Other commands, from other repositories
setup-video-vision
Interactive setup wizard for claude-video-vision — configure backend, whisper, frames, and verify dependencies.
create-epo-patent
Create a complete EPO-compliant patent application from invention disclosure through filing-ready package.
search-flights
Search award flight availability across airlines.
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
ui-audit
Run comprehensive UI/UX design validation against design principles, accessibility standards, and usability laws.
board-review
Quick board review - get expert opinions from 5 directors without full deliberation.