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 Plazmodium/odin-workflow --skill debugging-and-error-recoverygit clone --depth 1 https://github.com/Plazmodium/odin-workflowWrote 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/plazmodium/odin-workflow/debugging-and-error-recovery)<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/debugging-and-error-recovery"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/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/plazmodium/odin-workflow/debugging-and-error-recovery"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/debugging-and-error-recovery.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00026 | $0.00298 |
| Opus 5.5 | $0.00010 | $0.00119 |
| Sonnet 5.5 | $0.00005 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
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 1mo 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
debugging-and-error-recovery
When To Use
- Tests, builds, runtime behavior, or user reports fail.
- The root cause is unknown.
- A previous attempted fix did not work.
Workflow
- Reproduce the failure with the smallest reliable command or flow.
- Capture exact error text, inputs, environment, and expected behavior.
- Localize the failing component or boundary.
- Reduce the case to the smallest meaningful example.
- Fix the root cause, not the symptom.
- Add a regression guard when feasible.
- Rerun the failing check and the smallest relevant surrounding check.
Anti-Rationalization
| Excuse | Rebuttal |
|---|---|
| "I know what's wrong." | Reproduce first or risk fixing the wrong thing. |
| "I'll just silence the error." | Masking errors converts visible failures into latent defects. |
| "The first fix passed once." | Verify the guard and adjacent behavior. |
Verification
- Failure was reproduced or clearly not reproducible.
- Root cause is tied to evidence.
- The fix has a passing check and, when feasible, a regression test.
Exit Criteria
- The failure is fixed, guarded, and explained.
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.
- 1mo ago First seen · 43 lines · 26 tokens per session scan A bc780052d141
debugging-and-error-recovery is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 298 once invoked, about $0.0001 per session on Opus 5.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-09-01.
Other skills, from other repositories
mlflow-traces
Use when working with MLflow traces: debugging via MCP tools, analyzing performance, logging feedback, writing custom scorers/evaluations, or cleaning up trace data.
spotify-mcp-doctor
Diagnose and repair NovaLux12/spotify-mcp-server failures — auth, permissions, devices, rate limits, OpenClaw wiring. Use when Spotify tool calls fail or setup stalls.
feedback-nudge
Use when the user wants to report a bug, request a feature, or send feedback to the Zooza engineering team. Also offer proactively after a successful commit operation (max once per week).
progressive-delivery
Remediate a live production failure through a gated loop: reproduce the failure, generate a candidate fix, evaluate it, red-team it adversarially, then shadow, canary, and promote or roll back on SLO verdicts. Use when production is degraded and the fix must itself be proven safe, or when the user is already…
hmem-new-error
Create a new E-entry (bug/error) in hmem with the strict 5-level scaffold. Use when the user wants to log a bug, file a report, or document an error ('Bug loggen', 'log this error', 'Fehler eintragen'), or before any writememory with prefix='E'.
Safe Android Reverser
Safely fingerprint, route, decompile, inspect Flutter AOT, query program evidence, and reconstruct Android network/auth/crypto behavior through one capability-aware MCP control plane.