status

status is a command for Claude Code from Taoidle/plan-cascade. It costs 27 tokens per session (915 once invoked), scanned A, a copy of hybrid-status, MIT.

A command that shows the progress of stories in a PRD, where each story is a defined piece of project work.

In plain words
What is it for?
Use it to read the project's PRD and progress records, display each story's state, and review overall execution status.
Why use it?
It provides one view of completed and unfinished work, batch progress, completion percentage, and recent activity instead of requiring manual file checking.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the plan-cascade plugin — 7 skills, 33 commands shipped together

Good fit Use it to read the project's PRD and progress records, display each story's state, and review overall execution status.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/taoidle/plan-cascade/status
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.

Clone the repo
git clone --depth 1 https://github.com/Taoidle/plan-cascade

Made for: Claude Code.

Or install plan-cascade, the plugin that ships this one along with the rest of its 7 skills, 33 commands.

Wrote 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.

agentmods badge for status

README.md
[![agentmods](https://agentmods.dev/badge/commands/taoidle/plan-cascade/status/github.svg)](https://agentmods.dev/commands/taoidle/plan-cascade/status)
Your own site
<a href="https://agentmods.dev/commands/taoidle/plan-cascade/status"><img src="https://agentmods.dev/badge/commands/taoidle/plan-cascade/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.

agentmods 80×15 button for status

Your own site · 80×15
<a href="https://agentmods.dev/commands/taoidle/plan-cascade/status"><img src="https://agentmods.dev/badge/commands/taoidle/plan-cascade/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 915 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod 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.1 $0.00027 $0.00915
Opus 5.5 $0.00011 $0.00366
Sonnet 5.5 $0.00005 $0.00183
Haiku 4.5 $0.00003 $0.00092

Measured 1mo ago against content hash ab458e7aa95b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

Origin

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.

skills/hybrid-ralph/commands/status.md · 157 lines

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.txt in working directory

User-visible files always remain in the working directory for easy access.

Tool Usage Policy (CRITICAL)

To avoid command confirmation prompts:

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

    • Read("prd.json"), Read("progress.txt")
  2. Use Grep tool for content search - NEVER use grep via Bash

    • Grep("[COMPLETE]", path="progress.txt")
  3. 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.txt contains [COMPLETE] {story_id} or [STORY_COMPLETE] {story_id}
  • In Progress: If progress.txt contains [IN_PROGRESS] {story_id}
  • Pending: If no entry in progress.txt
  • Failed: If progress.txt contains [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}

...

============================================================

Read the full file on GitHub · 157 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. 1mo ago First seen · 157 lines · 27 tokens per session scan A ab458e7aa95b

Subscribe to this mod's changes

status is a command published in the GitHub repository Taoidle/plan-cascade (133 stars, last pushed 7mo ago), licensed MIT. It adds 27 tokens to every session and 915 once invoked, about $0.0001 per session on Opus 5.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.