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.
npx agentmods add commands/taoidle/plan-cascade/statusgit clone --depth 1 https://github.com/Taoidle/plan-cascadeWhat 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.00027 | $0.00915 |
| Opus 5 | $0.00014 | $0.00458 |
| Sonnet 5 | $0.00005 | $0.00183 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
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.
This is a copy
86% identical to hybrid-status — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hybrid Ralph - Show Execution Status
You are displaying the current execution status of all stories in the PRD.
Path Storage Modes
This command works with both new and legacy path storage modes:
New Mode (Default)
- PRD file: In worktree or
~/.plan-cascade/<project-id>/prd.json - Progress file: Always in working directory
progress.txt - Agent outputs:
.agent-outputs/in working directory
Legacy Mode
- PRD file: In worktree or project root
prd.json - Progress file:
progress.txtin working directory
User-visible files always remain in the working directory for easy access.
Tool Usage Policy (CRITICAL)
To avoid command confirmation prompts:
-
Use Read tool for file reading - NEVER use
catvia Bash- Read("prd.json"), Read("progress.txt")
-
Use Grep tool for content search - NEVER use
grepvia Bash- Grep("[COMPLETE]", path="progress.txt")
-
Parse file contents in your response - After reading with Read tool, count markers yourself
Step 1: Verify PRD Exists
if [ ! -f "prd.json" ]; then
echo "ERROR: No PRD found."
exit 1
fi
Step 2: Read PRD and Progress Files
Read prd.json to get all stories.
Read progress.txt to get completion status.
Step 3: Calculate Story Status
For each story in the PRD, determine its status:
- Complete: If
progress.txtcontains[COMPLETE] {story_id}or[STORY_COMPLETE] {story_id} - In Progress: If
progress.txtcontains[IN_PROGRESS] {story_id} - Pending: If no entry in
progress.txt - Failed: If
progress.txtcontains[FAILED] {story_id}or[STORY_FAILED] {story_id}or[ERROR] {story_id}
Step 4: Calculate Execution Batches
Re-calculate batches based on story dependencies.
Step 5: Display Status Report
============================================================
EXECUTION STATUS
============================================================
## Summary
Total Stories: {count}
Total Batches: {batch_count}
Complete: {complete_count} ●
In Progress: {in_progress_count} ◐
Pending: {pending_count} ○
Failed: {failed_count} ✗
## Progress
[{progress_bar}] {percentage}%
## Current Batch: {current_batch_number}
{stories in current batch with their statuses}
## All Batches
Batch 1: {status} ({count} stories)
{story statuses}
Batch 2: {status} ({count} stories)
{story statuses}
...
============================================================
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 · 157 lines · 27 tokens per session scan A ab458e7aa95b
status is a command published in the GitHub repository Taoidle/plan-cascade (131 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 915 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to hybrid-status, differing in 16 lines, and is treated as a copy.
Other commands, from other repositories
conv_release
Command "conv_release" from John-Wendell/Attention-MoA, covering chatbot arena conversations, all conversations and prompt distribution.
data_cleaning
Command "data_cleaning" from John-Wendell/Attention-MoA, covering data cleaning, requirements, steps, convert html to markdown and keep or remove specific languages.
pypi
Command "pypi" from John-Wendell/Attention-MoA, covering requirement and upload.
local_cluster
node-01.
webserver
Command "webserver" from John-Wendell/Attention-MoA, covering install, launch servers, check the launch time, increase the limit of max open files and gradio edit (3.35.2).
leaderboard
Command "leaderboard" from John-Wendell/Attention-MoA, covering get logs, clean battle data, run elo analysis, copy files to hf space and update files on webserver.