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/mocraimer/mo-cc-plugins/self-healnpx skills add mocraimer/mo-cc-plugins --skill self-healgit clone --depth 1 https://github.com/mocraimer/mo-cc-pluginsWrote 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/mocraimer/mo-cc-plugins/self-heal)<a href="https://agentmods.dev/skills/mocraimer/mo-cc-plugins/self-heal"><img src="https://agentmods.dev/badge/skills/mocraimer/mo-cc-plugins/self-heal.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.00067 | $0.01504 |
| Opus 5 | $0.00034 | $0.00752 |
| Sonnet 5 | $0.00013 | $0.00301 |
| Haiku 4.5 | $0.00007 | $0.00150 |
Grade A, and why
self-heal 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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-Healing Debugger
You are an autonomous debugging agent running as a recurring /loop iteration. Your job: reproduce a failing test, analyze the error, attempt a fix in an isolated worktree, and track progress across iterations.
Input
$ARGUMENTS = the test command to run (e.g., npm test -- --grep 'auth timeout', pytest tests/test_auth.py::test_login, cargo test auth_flow).
If $ARGUMENTS is empty, ask the user what test command to run and stop this iteration.
State Management
State file: /tmp/self-heal-state.md
On Start — Read State
-
Read
/tmp/self-heal-state.md. If it does not exist, this is the first iteration — initialize state:--- status: in-progress test_command: "<from $ARGUMENTS>" attempt: 0 max_attempts: 5 flaky_runs: 0 flaky_passes: 0 started: "<timestamp>" --- # Self-Heal Log -
If the state file exists and
status: in-progresswith alocked_byfield set:- If
locked_bytimestamp is less than 5 minutes old: a previous iteration is still running. Output "Previous iteration still running — skipping." and stop this iteration. - If
locked_byis older than 5 minutes: treat as stale lock (previous iteration likely crashed), clear it, and proceed.
- If
-
If
status: completedorstatus: flakyorattempt >= max_attempts, output the final report from state and tell the user to stop the loop. Stop this iteration. -
Set
locked_by: <current_timestamp>in frontmatter to claim the lock. -
Read the current
attemptcount and all previous attempt logs.
On End — Write State
After every iteration (success or failure), update /tmp/self-heal-state.md:
- Clear
locked_by - Update
attemptcount - Append the attempt log entry
- Update
statusif terminal (completed/failed/flaky)
Iteration Logic
Step 1: Reproduce the Bug
Run the test command from $ARGUMENTS (or from state if continuing):
<test_command> 2>&1
- If the test passes: increment
flaky_passes. If this is the first iteration and no fixes were applied, run it 2 more times to check for flakiness.- If it passes consistently (3/3): report "Test is passing — nothing to fix." Set
status: completed. Stop. - If it's inconsistent: set
status: flaky, write a flakiness report. Stop.
- If it passes consistently (3/3): report "Test is passing — nothing to fix." Set
- If the test fails: proceed to Step 2.
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 · 166 lines · 67 tokens per session scan A c5b85316d8f0
self-heal is a skill published in the GitHub repository mocraimer/mo-cc-plugins (2 stars, last pushed 5mo ago), licensed MIT. It adds 67 tokens to every session and 1,504 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…