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/custos/angry-ralph/angry-fixgit clone --depth 1 https://github.com/Custos/angry-ralphWrote 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/custos/angry-ralph/angry-fix)<a href="https://agentmods.dev/commands/custos/angry-ralph/angry-fix"><img src="https://agentmods.dev/badge/commands/custos/angry-ralph/angry-fix.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.00020 | $0.00316 |
| Opus 5 | $0.00010 | $0.00158 |
| Sonnet 5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
angry-fix 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 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.
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.
What it actually says
/angry-fix Command
Surgical post-pipeline TDD remediation. No planning. No review. Just fix and ship.
1. Argument Parsing
@filereferences (optional) -- File paths, error logs, test output as context.- Prompt text (required) -- Description of what to fix.
Example: /angry-fix @error.log "Fix the auth middleware timeout"
If no prompt:
Usage: /angry-fix [context] [prompt]
Example: /angry-fix @error.log "Fix the auth middleware timeout"
2. Procedure
- Read all provided
@filecontext. - Write a failing test that captures the expected correct behavior.
- Run the test suite — confirm the new test fails (red phase).
- Implement the fix — minimum code to make the test pass.
- Run the full test suite — confirm ALL tests pass (green phase).
- If tests fail, iterate: debug, fix, re-run.
- When all tests pass, create an atomic commit:
fix: <description from prompt>.
3. Constraints
- No planning artifacts created or modified.
- No review phase.
- No
.ralph-state/state modified. - Standalone surgical operation.
- Follow
references/tdd-protocol.mdfor TDD rules.
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 · 41 lines · 20 tokens per session scan A 07363c211c58
angry-fix is a command published in the GitHub repository Custos/angry-ralph (5 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 316 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.
Other commands, from other repositories
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
pm-auto-design2dev
設計レビューから実装完了まで完全自動化（設計レビュー→作業計画→TDD実装）.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
hub-tdd
TDD workflow for MCP Hub implementation. Types → Tests (red) → Implementation (green) with git gates.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.