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/GantisStorm/essentials-claude-codeWrote 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/gantisstorm/essentials-claude-code/show-status)<a href="https://agentmods.dev/commands/gantisstorm/essentials-claude-code/show-status"><img src="https://agentmods.dev/badge/commands/gantisstorm/essentials-claude-code/show-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/gantisstorm/essentials-claude-code/show-status"><img src="https://agentmods.dev/badge/commands/gantisstorm/essentials-claude-code/show-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.00009 | $0.01105 |
| Opus 5.5 | $0.00004 | $0.00442 |
| Sonnet 5.5 | $0.00002 | $0.00221 |
| Haiku 4.5 | $0.00001 | $0.00111 |
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 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 — 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 statusjson(no path) — List available prd.json filesbeads <epic-id>— Show bead status for an epicbeads --label <label>— Show bead status by labelbeads(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:
✓forpasses: true,○forpasses: 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
dependsOnare all done (passes: true) or empty - Blocked = pending tasks with unresolved
dependsOn - Done = tasks with
passes: true - All borders use box-drawing:
┌ ┐ └ ┘ ─ │ ┬ ┴ ├ ┤ ┼
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 · 122 lines · 9 tokens per session scan A bdadcb65e54d
show-status is a command published in the GitHub repository GantisStorm/essentials-claude-code (90 stars, last pushed 8mo ago), licensed Unlicense. It adds 9 tokens to every session and 1,105 once invoked, about $0.0000 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
report-issue-with-atomic
Open an issue against the atomic-claude repo itself (bugs/feature requests with the installed config, not the user's current project).
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.
feature-config
Phase 0 of develop: Configuration wizard, escape hatches, preferences, continuation detection.
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
polish-repo-community
Phase 3 of polish-repo: Community infrastructure, issue templates, roadmap, contributor experience, and signs of life.
create-issue
Create a GitHub issue with proper template discovery and population.