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-status)<a href="https://agentmods.dev/commands/taoidle/plan-cascade/mega-status"><img src="https://agentmods.dev/badge/commands/taoidle/plan-cascade/mega-status/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-status"><img src="https://agentmods.dev/badge/commands/taoidle/plan-cascade/mega-status.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.00023 | $0.01887 |
| Opus 5.5 | $0.00009 | $0.00755 |
| Sonnet 5.5 | $0.00005 | $0.00377 |
| Haiku 4.5 | $0.00002 | $0.00189 |
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 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 — 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:
-
Use Read tool for file reading - NEVER use
catvia Bash- ✅
Read("mega-plan.json"),Read(".mega-status.json") - ❌
Bash("cat mega-plan.json")
- ✅
-
Use Glob tool for finding files - NEVER use
lsorfindvia Bash- ✅
Glob(".worktree/*/progress.txt") - ❌
Bash("ls .worktree/")
- ✅
-
Use Grep tool for content search - NEVER use
grepvia Bash- ✅
Grep("[FEATURE_COMPLETE]", path="...") - ❌
Bash("grep '[FEATURE_COMPLETE]' ...")
- ✅
-
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 "{}"
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 · 276 lines · 23 tokens per session scan A 85acd92bfb15
mega-status is a command published in the GitHub repository Taoidle/plan-cascade (133 stars, last pushed 7mo ago), licensed MIT. It adds 23 tokens to every session and 1,887 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
poc
Before building on an unproven idea, get a timeboxed yes/no answer — start a hypothesis-driven POC that skips 80% of the production pipeline and forces ship/pivot/kill at expiry, then promote a shipped POC through the audits it skipped.
spec
Know the problem but not yet the product, the requirements or the design? Run it — you get, stage by stage, a discovery plan (/spec discover), a PRD (/spec prd) and a build spec: requirements.md + design.md + tasks.md (/spec or /spec build). Run before writing any code.
ownership
When you need to know who owns a path and who answers for it — the service ownership matrix (team, lead, on-call, SLA) auto-detected from git with CODEOWNERS generated, plus on-call rotations, shift handoffs and escalation paths.
rfc
RFC process for cross-team decisions. Create, track, and close RFCs. Accepted RFCs auto-create ADRs.
exception
Signed gate-exception registry — replace ad-hoc --admin / --no-verify bypasses with an auditable, signed, expiring record (who · why · gate · scope · expiry). Create / list / check exceptions.
conductor-new-track
Create a new development track with spec, plan, and metadata.