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/evoelsewhere/evoflux/self-healingnpx skills add evoelsewhere/evoflux --skill self-healinggit clone --depth 1 https://github.com/evoelsewhere/evofluxWrote 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/evoelsewhere/evoflux/self-healing)<a href="https://agentmods.dev/skills/evoelsewhere/evoflux/self-healing"><img src="https://agentmods.dev/badge/skills/evoelsewhere/evoflux/self-healing.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.00077 | $0.00828 |
| Opus 5 | $0.00039 | $0.00414 |
| Sonnet 5 | $0.00015 | $0.00166 |
| Haiku 4.5 | $0.00008 | $0.00083 |
Grade A, and why
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 3d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update agent configuration
Make surgical edits only under {EVOFLUX_CONFIG_DIR}/. Do not load bundled
references when this skill activates. Never edit application code, .env,
secrets, built-in tool definitions, or bundled/read-only agent profiles through
this workflow.
Route the request
- Agent model, thinking, fallback, prompt,
tools,tools_opt_out,skills, ormcpmetadata: continue here. - Install or update an MCP server: load
$mcp-installerinstead. - Create, import, or update a skill bundle: load
$skill-installerinstead. - Install a plugin: load
$plugin-installerinstead.
State machine
1. RESOLVE
Resolve the exact writable agent file. Use the current lead when “yourself” is
unambiguous; otherwise inspect {EVOFLUX_CONFIG_DIR}/agents/ by role: and
name:. Do not hard-code filenames. Ask only if multiple writable candidates
remain.
2. INSPECT
Read the complete current file before proposing a change. Preserve unrelated frontmatter, prompt text, comments, order, and formatting. If the file does not exist, treat the request as explicit creation and preserve the invariant that exactly one configured agent is the lead.
Read references/agent-config-contract.md
only when changing a model, thinking level, fallback, prompt, tools,
tools_opt_out, skills metadata, or creating a file. Read
references/mcp-agent-wiring.md only when
attaching, selecting, or removing MCP tools from an agent.
3. VALIDATE
Validate the requested value against runtime-visible state before editing:
- model/provider and advertised thinking levels must exist;
- tool names must come from the current registry;
- skill names must come from the current discovered catalog;
- MCP server/tool names must come from current MCP status when reachable;
- implicit lifecycle/team invariants cannot be opted out;
- never expose or probe more than whether a required credential is configured.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 88 lines · 77 tokens per session scan A 9ec7311833dc
self-healing is a skill published in the GitHub repository evoelsewhere/evoflux (5 stars, last pushed 7d ago), licensed Apache-2.0. It adds 77 tokens to every session and 828 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-31.
Other skills, from other repositories
rove
Use when controlling Rove tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell. Also the ONLY channel for messaging another agent session on this machine — rove api send, never a peer/MCP side channel.
E2E Testing Nori Skillsets Subcommands
Use when you need to interactively test a nori-skillsets CLI subcommand end-to-end via tmux, with full filesystem isolation.
general-video
The fallback workflow for authoring custom HyperFrames video compositions at any length or format — longer or multi-scene pieces, brand / sizzle reels, montages, title cards, static loops, and freeform compositions. Input- and length-agnostic. If a specialized workflow clearly fits the input — a marketed product, a…
release
Autonomously cut a Rove (@sma1lboy/rove) release end-to-end — detect the semver bump from pending changesets (flagging an upstream minor you didn't intend), run the release gates, bump/tag/push via scripts/release.sh, then poll the GitHub Actions Release workflow with gh until npm publish completes, diagnosing CI…
hyperframes-cli
HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, or remove-background, or when troubleshooting the…
changelog-generator
Draft Rove release notes as Changesets. Writes user-facing entries as .changeset/.md files for @sma1lboy/rove (consumed into packages/kobe/CHANGELOG.md at release time). Use when the user asks for "changelog", "release notes", "what changed", "add a changeset", or before cutting a version. Enforces Rove's no-soft-wrap…