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 ayushcodes10/echo-mem --skill source-command-automation-self-healinggit clone --depth 1 https://github.com/ayushcodes10/echo-memWrote 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/ayushcodes10/echo-mem/source-command-automation-self-healing)<a href="https://agentmods.dev/skills/ayushcodes10/echo-mem/source-command-automation-self-healing"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/source-command-automation-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/skills/ayushcodes10/echo-mem/source-command-automation-self-healing"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/source-command-automation-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.00018 | $0.00615 |
| Opus 5.5 | $0.00007 | $0.00246 |
| Sonnet 5.5 | $0.00004 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
source-command-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 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-automation-self-healing
Use this skill when the user asks to run the migrated source command automation-self-healing.
Command Template
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__claude-flow__memory_usage({
"action": "store",
"key": "error-pattern-" + Date.now(),
"value": JSON.stringify(errorData),
"namespace": "error-patterns",
"ttl": 2592000 // 30 days
})
// Analyze patterns
mcp__claude-flow__neural_patterns({
"action": "analyze",
"operation": "error-recovery",
"outcome": "success"
})
Self-Healing Integration
MCP Tool Coordination
// Initialize self-healing swarm
mcp__claude-flow__swarm_init({
"topology": "star",
"maxAgents": 4,
"strategy": "adaptive"
})
// Spawn recovery agents
mcp__claude-flow__agent_spawn({
"type": "monitor",
"name": "Error Monitor",
"capabilities": ["error-detection", "recovery"]
})
// Orchestrate recovery
mcp__claude-flow__task_orchestrate({
"task": "recover from error",
"strategy": "sequential",
"priority": "critical"
})
Fallback Hook Configuration
{
"PostToolUse": [{
"matcher": "^Bash$",
"command": "npx Codex-flow hook post-bash --exit-code '${tool.result.exitCode}' --auto-recover"
}]
}
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 · 118 lines · 18 tokens per session scan A bb37e8cadd4e
source-command-automation-self-healing is a skill published in the GitHub repository ayushcodes10/echo-mem (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 615 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-12.
Other skills, from other repositories
impact-trace
For a change point (function / type / endpoint / SQL column), enumerate its real blast radius across six dimensions with a grep citation per row, then derive the regression test scope. Every impact-table row must trace to a real search hit — never a self-asserted claim.
test-runner
For a code change, pick the right test tier by change surface, run apc test with baseline diff, and report only NEW reds vs baseline back to the task's acceptance criterion. Separates envblocked from SUT red so a broken machine never fails the code.
neqsim-regression-baselines
Regression baseline management for NeqSim. USE WHEN: modifying solver logic, property correlations, or EOS implementations. Ensures changes don't silently degrade accuracy. Covers creating baseline fixtures, writing regression tests, and detecting accuracy drift.
pytest.fix_local_tests
Analyze and fix failure of local tests.
compiler-11897630
A coverage skill that marks or reports how much of a set of instructions is covered by tests. Test coverage is a measure of which code paths tests exercise.
diagnosing-bugs
Build a tight, red-capable feedback loop before diagnosing failures, then minimize, test ranked hypotheses, and lock the fix with a regression test.