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 OutlineDriven/outline-driven-development --skill fail-recovergit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/fail-recover)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/fail-recover"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/fail-recover/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/outlinedriven/outline-driven-development/fail-recover"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/fail-recover.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 44 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00066 | $0.00810 |
| Opus 5 | $0.00033 | $0.00405 |
| Sonnet 5 | $0.00013 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
fail-recover 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- fail-recover — 88% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fail recover
Contract
| Field | Bound contract |
|---|---|
| Trigger | User needs to restore service from a specific known failure using a prescribed recovery operation. |
| Authority | Reversible local writes only. State and follow the rollback path before mutating. Write only the named local target. |
| Side effect | The single prescribed recovery operation applied to the local configuration target. No scope widening, no retry with a different action. |
| Done | The recovery operation is applied to the target artifact and the health signal confirms service restoration. |
Inputs
Required:
- The known failure symptom: the observable condition that identifies the failure (error message, metric threshold, health-check output).
- The prescribed recovery operation: the single bounded action to apply.
- The authority source for the prescription: where the recovery operation is documented (a runbook, an incident postmortem, a vendor advisory, a playbook entry). Named explicitly so the operation can be validated.
- The target configuration artifact: the local file, setting, or service the operation changes.
Optional:
- An explicit rollback path. If absent, derive and record one before any mutation.
- A health signal or verification mechanism: the command, endpoint, or metric that confirms restoration. If absent, ask the user to name one before applying the operation.
Procedure
- Verify the observed symptom matches the known failure. Compare the observed condition against the documented symptom. If they do not match, stop. Done when: the symptom matches the known failure, or the skill stops with the mismatch reported.
- Validate the prescribed recovery operation against the named authority source. Confirm the operation is the one documented for this failure and that it targets only the named local artifact. If the authority source does not prescribe this operation for this symptom, stop. Done when: the operation is validated as prescribed and scoped to the named target.
- Record the explicit rollback path that reverses the recovery operation. If the user did not supply one, derive it from the operation's inverse and record it before any mutation. Done when: the rollback path is recorded.
- Apply the recovery operation to the named local target only. Done when: the recovery operation is applied to the named target.
- Verify restoration using the specified health signal or verification mechanism. Run the health check, query the endpoint, or read the metric. Done when: the health signal confirms service restoration, or the check fails and rollback is triggered.
What ships with it
1 file 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.
- 5d ago First seen · 51 lines · 66 tokens per session scan A 75d6430a8246
fail-recover is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 3d ago), licensed Apache-2.0. It adds 66 tokens to every session and 810 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-09-03.
Other skills, from other repositories
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
debug
Hypothesis-driven debugging. Use when a test fails, a crash or exception occurs, output is wrong, or an intermittent flake has no obvious cause.
optimize
Use when asked to optimize code, speed up a path, reduce allocations, repair a regression, or profile a target. Not for remote, credential, publish, deploy, or irreversible changes.
ios-build-fix
Use when asked to run /ios-build-fix to fix a failing iOS build, regenerate an Xcode project from project.yml, or correct UI behavior. Not for a clean rebuild: use ios-build-cleanup.
strike-the-root
Use when a bug, failure, flake, regression, review finding, or ticket needs the core fixed so it cannot recur. Not for greenfield features: use tdd. Not for style-only review or typo-class one-liners.
extremely-optimize
Use when asked to run a performance campaign against a measured floor. Not for hypothesis-only analysis without mutation: use fastopt.