mega-status

A status command for a mega-plan, which is a plan that coordinates several project features and their dependencies. It reports progress for features and the stories within them.

In plain words
What is it for?
Use it to inspect feature progress, story completion, and the saved status of a mega-plan.
Why use it?
It gives you one place to see how a multi-feature project is progressing and what remains unfinished.

Command

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-status
Clone the repo
git clone --depth 1 https://github.com/Taoidle/plan-cascade
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,887 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.00023 $0.01887
Opus 5 $0.00012 $0.00944
Sonnet 5 $0.00005 $0.00377
Haiku 4.5 $0.00002 $0.00189

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

Security

Grade A, and why

mega-status 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-status.md · 276 lines

How it starts

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

Mega Plan Status

Display comprehensive status of the mega-plan execution.

Path Storage Modes

This command works with both new and legacy path storage modes:

New Mode (Default)

  • mega-plan.json: ~/.plan-cascade/<project-id>/mega-plan.json
  • .mega-status.json: ~/.plan-cascade/<project-id>/.state/.mega-status.json
  • Worktrees: ~/.plan-cascade/<project-id>/.worktree/<feature>/

Legacy Mode

  • All files in project root

The command uses PathResolver to find files in the correct locations.

Tool Usage Policy (CRITICAL)

To avoid command confirmation prompts:

  1. Use Read tool for file reading - NEVER use cat via Bash

    • Read("mega-plan.json"), Read(".mega-status.json")
    • Bash("cat mega-plan.json")
  2. Use Glob tool for finding files - NEVER use ls or find via Bash

    • Glob(".worktree/*/progress.txt")
    • Bash("ls .worktree/")
  3. Use Grep tool for content search - NEVER use grep via Bash

    • Grep("[FEATURE_COMPLETE]", path="...")
    • Bash("grep '[FEATURE_COMPLETE]' ...")
  4. Only use Bash for actual system commands (git, mkdir, etc.)

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 State

Read the mega-plan and sync status from worktrees:

# Get file paths 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")
MEGA_STATUS_PATH=$(uv run python -c "from plan_cascade.state.path_resolver import PathResolver; from pathlib import Path; print(PathResolver(Path.cwd()).get_mega_status_path())" 2>/dev/null || echo ".mega-status.json")

cat "$MEGA_PLAN_PATH"
cat "$MEGA_STATUS_PATH" 2>/dev/null || echo "{}"

Read the full file on GitHub · 276 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. 2d ago First seen · 276 lines · 23 tokens per session scan A 85acd92bfb15

Subscribe to this mod's changes

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