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 skills add lukas-grigis/ralphctl --skill ralphctl-debugging-and-error-recoverygit clone --depth 1 https://github.com/lukas-grigis/ralphctlWrote 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/skills/lukas-grigis/ralphctl/ralphctl-debugging-and-error-recovery)<a href="https://agentmods.dev/skills/lukas-grigis/ralphctl/ralphctl-debugging-and-error-recovery"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-debugging-and-error-recovery/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/skills/lukas-grigis/ralphctl/ralphctl-debugging-and-error-recovery"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-debugging-and-error-recovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.02205 |
| Opus 5 | $0.00039 | $0.01103 |
| Sonnet 5 | $0.00016 | $0.00441 |
| Haiku 4.5 | $0.00008 | $0.00220 |
Grade A, and why
ralphctl-debugging-and-error-recovery 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 9d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging and Error Recovery
Adapted from addyosmani/agent-skills (MIT). Adapted for ralphctl's harness contract.
Systematic debugging with structured triage. When something breaks, stop adding features, preserve evidence, and follow a structured process to find and fix the root cause. Guessing wastes time. The triage checklist works for test failures, build errors, runtime bugs, and unexpected behaviour across any project ecosystem.
When this applies
- Refine — when a bug is part of the acceptance criteria, name it as a checkable predicate (reproduce + expected vs actual), not vague prose.
- Plan — when tasks involve fixing existing failures, order them reproduce → localize → fix → guard so each task has a clear entry/exit contract.
- Execute — whenever something unexpected happens during implementation: a test fails, the build breaks, behaviour diverges from the spec. Stop, triage, fix the root cause, then resume.
The Stop-the-Line Rule
When anything unexpected happens:
- Stop adding features or making unrelated changes.
- Preserve evidence — error output, logs, repro steps. Do not overwrite or discard.
- Diagnose using the triage checklist below.
- Fix the root cause, not the symptom.
- Guard against recurrence by including a regression test in the same change.
- Resume only after the fix is verified with the project's narrow check gate.
Do not push past a failing test or broken build to work on the next feature. Errors compound — a bug at Step 3 that goes unfixed makes Steps 4–10 wrong.
The Triage Checklist
Work through these steps in order. Do not skip steps.
Step 1: Reproduce
Make the failure happen reliably. If you cannot reproduce it, you cannot fix it with confidence.
When a bug is non-reproducible, work through these branches:
- Timing-dependent — add timestamps to logs near the suspected area; try with artificial delays to widen race windows; run under load or concurrency to increase collision probability.
- Environment-dependent — compare runtime versions, OS, environment variables; check for differences in data (empty vs populated); try reproducing in a clean environment.
- State-dependent — check for leaked state between tests or requests; look for global variables, singletons, or shared caches; run the failing scenario in isolation.
- Truly random — add defensive logging at the suspected location; document the conditions observed and revisit when it recurs.
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.
- 9d ago First seen · 192 lines · 78 tokens per session scan A b1e2496cd2b7
ralphctl-debugging-and-error-recovery is a skill published in the GitHub repository lukas-grigis/ralphctl (23 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 2,205 once invoked, about $0.0004 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
debugging
Use when debugging bugs, test failures, or unexpected behavior. Triggers: 'why isn't this working', 'this doesn't work', 'X is broken', 'something's wrong', 'getting an error', 'exception in', 'stopped working', 'regression', 'crash', 'hang', 'flaky test', 'intermittent failure', or when user pastes a stack…
bug-fix
A structured bug-fixing workflow that takes a problem from reproduction and evidence-based cause finding through approval, implementation, testing, and cleanup.
qa-cycle
QA + bugfix cycle until it passes.
vitest
You are writing tests with Vitest. Apply these conventions.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.