show-status

A command that displays a formatted summary of task records or Beads work items. Beads are tracked units of development work, while a PRD is a product-requirements document stored as JSON.

In plain words
What is it for?
Use it to show a PRD task dashboard, list available PRD files, view an epic's Beads, or filter Beads by label.
Why use it?
It gives you a quick view of progress, dependencies, and available task files without reading the raw data manually.

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/gantisstorm/essentials-claude-code/show-status
Clone the repo
git clone --depth 1 https://github.com/GantisStorm/essentials-claude-code
Per session 9 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,105 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.00009 $0.01105
Opus 5 $0.00005 $0.00553
Sonnet 5 $0.00002 $0.00221
Haiku 4.5 $0.00001 $0.00111

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

Security

Grade A, and why

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

essentials/commands/show-status.md · 122 lines

How it starts

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

Show Status

Show a formatted status dashboard for tasks (prd.json) or beads.

Arguments

  • json <path> — Show prd.json task status
  • json (no path) — List available prd.json files
  • beads <epic-id> — Show bead status for an epic
  • beads --label <label> — Show bead status by label
  • beads (no args) — List recent epics

Instructions

Parse $ARGUMENTS to determine mode.

If $ARGUMENTS is empty or invalid:

Usage: /show-status <json|beads> [path|epic-id]

  json <path>       Show prd.json task status
  beads <epic-id>   Show bead status for an epic
  beads -l <label>  Show bead status by label

If $ARGUMENTS starts with json:

If path provided, read the raw JSON:

cat "<path>"

Parse the JSON output and render a dashboard using box-drawing characters. Follow this exact format:

┌─────────────────────────────────────────────────────────┐
│  Feature Name                                           │
├────────┬──────────────────────────────┬────────┬────────┤
│ ID     │ Title                        │ Status │ Deps   │
├────────┼──────────────────────────────┼────────┼────────┤
│ US-001 │ Create auth types            │   ✓    │        │
│ US-002 │ Implement token exchange     │   ○    │ US-001 │
│ US-003 │ Add login route              │   ○    │ US-002 │
├────────┴──────────────────────────────┴────────┴────────┤
│  Progress: 1/3 done  ████░░░░░░░░ 33%                   │
│  Ready: 1  Blocked: 1  Done: 1                          │
└─────────────────────────────────────────────────────────┘

Formatting rules:

  • for passes: true, for passes: false
  • Column widths: auto-size to longest value in each column, pad with spaces
  • Progress bar: 12 chars wide using (filled) and (empty), rounded to nearest block
  • Ready = pending tasks whose dependsOn are all done (passes: true) or empty
  • Blocked = pending tasks with unresolved dependsOn
  • Done = tasks with passes: true
  • All borders use box-drawing: ┌ ┐ └ ┘ ─ │ ┬ ┴ ├ ┤ ┼

Read the full file on GitHub · 122 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 · 122 lines · 9 tokens per session scan A bdadcb65e54d

Subscribe to this mod's changes

show-status is a command published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 9 tokens to every session and 1,105 once invoked, about $0.0000 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.