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/peaky8linders/claude-cortex/ralph-statusgit clone --depth 1 https://github.com/Peaky8linders/claude-cortexWrote 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/peaky8linders/claude-cortex/ralph-status)<a href="https://agentmods.dev/commands/peaky8linders/claude-cortex/ralph-status"><img src="https://agentmods.dev/badge/commands/peaky8linders/claude-cortex/ralph-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.00026 | $0.00362 |
| Opus 5 | $0.00013 | $0.00181 |
| Sonnet 5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade B, and why
ralph-status scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/knowledge/.ralph-active 2>/dev/null What it actually says
/ralph-status — Monitor Autonomous Loop
Show the current state of an active Ralph Wiggum loop without modifying it.
Protocol
Step 1: Check Loop State
cat ~/.claude/knowledge/.ralph-active 2>/dev/null
If no loop file exists, report: "No active Ralph loop." and stop.
If loop is active, extract from .ralph-active:
prompt: The task being worked oniteration: Current iteration numbermax_iterations: Maximum allowedscope: Directory boundary (if any)started_at: When the loop was activated
Display Dashboard
+------------------------------------------+
| RALPH LOOP STATUS |
+------------------------------------------+
| Task: {prompt} |
| Scope: {scope or "entire project"} |
| Iteration: {iteration}/{max_iterations} |
| Quality: {score}/100 |
| Started: {started_at} |
| Elapsed: {duration} |
| Commits: {commit_count} since start |
| Files: {files_changed} modified |
+------------------------------------------+
Health Assessment
- Healthy: Quality >= 50, no errors, steady commits
- Warning: Quality 40-50, or errors present, or no commits in last iteration
- Critical: Quality < 40 (will halt on next iteration)
Do NOT modify any files. This is read-only.
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.
- 4d ago First seen · 49 lines · 26 tokens per session scan B b84cafe23781
ralph-status is a command published in the GitHub repository Peaky8linders/claude-cortex (11 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 362 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
clarify
Walk through inbox items applying the GTD decision tree. Usage: /gtd:clarify [--id gtd-xxx].