angry-status

angry-status is a command for coding agents from Custos/angry-ralph. It costs 12 tokens per session (224 once invoked), scanned A, original, MIT.

A read-only command that shows the current state of an angry-ralph software-development workflow. It reports the active phase, completed phases, review setup, and any active implementation loop.

In plain words
What is it for?
Use it to check pipeline progress, completion markers, review settings, and the currently running section.
Why use it?
It gives you a quick view of what has been completed and where the workflow stopped. If no workflow is active, it reports that instead.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the angry-ralph plugin — 1 skill, 8 commands, 1 agent, 2 hooks shipped together

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/custos/angry-ralph/angry-status
Clone the repo
git clone --depth 1 https://github.com/Custos/angry-ralph

Or install angry-ralph, the plugin that ships this one along with the rest of its 1 skill, 8 commands, 1 agent, 2 hooks.

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 angry-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/custos/angry-ralph/angry-status.svg)](https://agentmods.dev/commands/custos/angry-ralph/angry-status)
Your own site
<a href="https://agentmods.dev/commands/custos/angry-ralph/angry-status"><img src="https://agentmods.dev/badge/commands/custos/angry-ralph/angry-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 224 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.1 $0.00012 $0.00224
Opus 5 $0.00006 $0.00112
Sonnet 5 $0.00002 $0.00045
Haiku 4.5 $0.00001 $0.00022

Measured 5d ago against content hash a7f50ad3cf34, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

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

commands/angry-status.md · 33 lines

What it actually says

/angry-status Command

Display the current pipeline state at a glance. Read-only — no side effects.

Procedure

1. Check for Pipeline State

Run via the Bash tool:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/lib/pipeline.sh status .

This reads .ralph-state/pipeline.json and .ralph-state/loop.md, checks .done markers, and prints a formatted summary:

angry-ralph status:
  Phase:        <current_phase>
  Completed:    <comma-separated completed_phases>
  Done markers: architect[✓/✗] review[✓/✗] execute[✓/✗]
  Review tier:  <tier> (<reviewers>)
  Config:       .ralph-state/pipeline.json
  Loop:         <section> (iteration <N>) [active|inactive]

If no pipeline state exists, it prints: "No active angry-ralph pipeline."

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. 5d ago First seen · 33 lines · 12 tokens per session scan A a7f50ad3cf34

Subscribe to this mod's changes

angry-status is a command published in the GitHub repository Custos/angry-ralph (5 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 224 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-31.