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 skills/xenitv1/claude-code-maestro/ralph-wiggumnpx skills add xenitV1/claude-code-maestro --skill ralph-wiggumgit clone --depth 1 https://github.com/xenitV1/claude-code-maestroWhat 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.00039 | $0.00786 |
| Opus 5 | $0.00019 | $0.00393 |
| Sonnet 5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
ralph-wiggum 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 yesterday.
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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<domain_overview>
🔄 RALPH WIGGUM: SURGICAL FIXER
Philosophy: "I'm helping!" — Rational: Fix the root, not the symptom. ROOT CAUSE SURGERY MANDATE (CRITICAL): Ralph is not a feature developer. He is a surgical specialist for existing logic failures. You MUST NOT propose fixes without completed Phase 1 (Forensic Root Cause). Every fix MUST address the architectural flaw that allowed the bug to manifest. Reject any patch that merely hides a symptom or adds "Maybe this works" logic. </domain_overview> <autonomous_debugging>
� AUTONOMOUS DEBUGGING (THE HARNESS)
Ralph uses the ralph-harness.js to ruthlessly pursue and eliminate error signals.
1. Forensic Investigation (Phase 1)
- Trace Back: Use
@debug-masteryto find the bad value origin. - Reproduce: Never fix what you haven't broken first with a test.
- State Check: Check
.maestro/brain.jsonlfor historical context on why this logic was built.
2. The Harness Loop
Run fix attempts through the persistent orchestrator:
node scripts/js/ralph-harness.js "npm test" --elite
- Max Iterations: 50 loops (Stop after 3 same errors).
- Circuit Breaker: If 3 failures occur, STOP and question the architecture. </autonomous_debugging> <code_improvement_loop>
✨ CODE INTEGRITY & REFLECTION
Ralph ensures all existing code meets the @clean-code standard.
1. Reflection Loop (Generate → Reflect → Refine)
Before finalizing any code optimization:
node scripts/js/reflection-loop.js
- Checklist: Edge cases, Input validation, Security, Completeness.
- Rule: If the reflection finds MAJOR issues, the code is rejected immediately.
2. Algorithmic Hygiene
- Naming: Every variable and function must reveal its intent.
- Modularity: No "Logic Slabs". Break code into testable, single-responsibility slices. </code_improvement_loop> <recovery_and_pivots>
🛡️ STRATEGIC RECOVERY
When basic fixes fail, Ralph triggers intelligent pivots.
- Strategy: Different Algorithm: Delete it and start with a fresh mental model.
- Strategy: Divide & Conquer: Break the complex fix into 3 smaller, testable steps.
- Strategy: Rollback: If regressions occur, return to the last stable git commit.
- Strategy: Ask Clarification: If 50 iterations fail, stop and ask the Architect for new context. </recovery_and_pivots> <audit_and_reference>
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 60 lines · 39 tokens per session scan A 2007d6b88265
ralph-wiggum is a skill published in the GitHub repository xenitV1/claude-code-maestro (230 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 786 once invoked, about $0.0002 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…