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.
git clone --depth 1 https://github.com/monoes/monomindWrote 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/monoes/monomind/self-healing)<a href="https://agentmods.dev/commands/monoes/monomind/self-healing"><img src="https://agentmods.dev/badge/commands/monoes/monomind/self-healing/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/commands/monoes/monomind/self-healing"><img src="https://agentmods.dev/badge/commands/monoes/monomind/self-healing.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.00017 | $0.00497 |
| Opus 5.5 | $0.00007 | $0.00199 |
| Sonnet 5.5 | $0.00003 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
automation:self-healing 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.
This is a copy
88% identical to self-healing — 49 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Self-Healing Workflows
Purpose
Automatically detect and recover from errors without interrupting your flow.
Self-Healing Features
1. Error Detection
Monitors for:
- Failed commands
- Syntax errors
- Missing dependencies
- Broken tests
2. Automatic Recovery
Missing Dependencies:
Error: Cannot find module 'express'
→ Automatically runs: npm install express
→ Retries original command
Syntax Errors:
Error: Unexpected token
→ Analyzes error location
→ Suggests fix through analyzer agent
→ Applies fix with confirmation
Test Failures:
Test failed: "user authentication"
→ Spawns debugger agent
→ Analyzes failure cause
→ Implements fix
→ Re-runs tests
3. Learning from Failures
Each recovery improves future prevention:
- Patterns saved to knowledge base
- Similar errors prevented proactively
- Recovery strategies optimized
Pattern Storage:
// Store error patterns
mcp__monomind__memory_pattern-store({
key: "error-pattern-" + Date.now(),
value: JSON.stringify(errorData),
namespace: "error-patterns",
ttl: 2592000 // 30 days
})
// Analyze patterns
mcp__monomind__hooks_intelligence_pattern-search({
query: "error-recovery success"
})
Self-Healing Integration
MCP Tool Coordination
// Spawn recovery agents
mcp__monomind__agent_spawn({
"type": "monitor",
"name": "Error Monitor",
"capabilities": ["error-detection", "recovery"]
})
// Orchestrate recovery
mcp__monomind__task_create({
description: "recover from error",
strategy: "sequential",
priority: "critical"
})
Fallback Hook Configuration
{
"PostToolUse": [{
"matcher": "^Bash$",
"command": "npx monomind hooks post-command --command \"$TOOL_INPUT_command\" --success \"$TOOL_SUCCESS\""
}]
}
Benefits
- Resilient workflows
- Automatic recovery
- Learns from errors
- Saves debugging time
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 · 101 lines · 17 tokens per session scan A 587facd3322d
automation:self-healing is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 497 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to self-healing, differing in 49 lines, and is treated as a copy.
Other commands, from other repositories
self-healing
Automatically detect and recover from errors without interrupting your flow.
build-fix
Systematically investigate and fix build errors, TypeScript errors, or test failures with minimal diffs.
doctor
Health-check the harness: kernel load, MCP wiring, memory backend, host adapter.
verify
Run verification loop to validate implementation.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
self-healing
Automatically detect and recover from errors without interrupting your flow.