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/hybrid-statusgit 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/hybrid-status)<a href="https://agentmods.dev/commands/taoidle/plan-cascade/hybrid-status"><img src="https://agentmods.dev/badge/commands/taoidle/plan-cascade/hybrid-status.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.00973 |
| Opus 5 | $0.00014 | $0.00487 |
| Sonnet 5 | $0.00005 | $0.00195 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
hybrid-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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- status — 86% identical, 16 lines differ
How it starts
The opening of the file, as written. The whole thing — 159 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") - ❌
Bash("cat prd.json")
- ✅
-
Use Grep tool for content search - NEVER use
grepvia Bash- ✅
Grep("[COMPLETE]", path="progress.txt") - ❌
Bash("grep '[COMPLETE]' 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.
- 5d ago First seen · 159 lines · 27 tokens per session scan A 5a2d04b59e60
hybrid-status is a command published in the GitHub repository Taoidle/plan-cascade (140 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 973 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.
Other commands, from other repositories
setup-video-vision
Interactive setup wizard for claude-video-vision — configure backend, whisper, frames, and verify dependencies.
doctor
Health check for greatcto. Shows pipeline state, missing artefacts, hook status, last run per agent, and permission-denied tail.
review
12-angle code review + skeptical triage (3-round + arbiter) for security/reliability P0/P1 findings, OR traceability tree. Default: review current branch vs main. --deep: triage ALL P0/P1 angles (not just security). With trace : render REQ → IMPL → TEST tree for impact analysis. Creates or closes gate:code for…
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
ccr
CCR (Compressed Context with Retrieval) — recall the full original of context that greatcto compressed/filtered out, by its short id. The retrieval half of the compression layer.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.