Borrowing it
Nothing to install: this file belongs to oaslananka/debug-recorder-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/oaslananka/debug-recorder-mcp/main/.opencode/skills/incident-replay/SKILL.mdgit clone --depth 1 https://github.com/oaslananka/debug-recorder-mcpWrote 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/oaslananka/debug-recorder-mcp/incident-replay)<a href="https://agentmods.dev/skills/oaslananka/debug-recorder-mcp/incident-replay"><img src="https://agentmods.dev/badge/skills/oaslananka/debug-recorder-mcp/incident-replay/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/oaslananka/debug-recorder-mcp/incident-replay"><img src="https://agentmods.dev/badge/skills/oaslananka/debug-recorder-mcp/incident-replay.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.00028 | $0.00127 |
| Opus 5 | $0.00014 | $0.00063 |
| Sonnet 5 | $0.00006 | $0.00025 |
| Haiku 4.5 | $0.00003 | $0.00013 |
Grade A, and why
incident-replay 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 12d 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.
What it actually says
Incident Replay Skill
Use this skill when a user asks whether an error has happened before, how it was fixed, or how to reproduce a previous incident.
Workflow
- Search for similar errors and relevant sessions.
- Inspect the most relevant sessions.
- Extract symptoms, commands, failed fixes, successful fixes, and environment notes.
- Summarize what is reusable and what must be revalidated.
- Recommend the next debugging action.
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.
- 12d ago First seen · 17 lines · 28 tokens per session scan A 77567d73bb4f
incident-replay is a skill published in the GitHub repository oaslananka/debug-recorder-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 127 once invoked, about $0.0001 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
Scientific root-cause isolation and step-by-step resolution of complex runtime bugs.
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
systematic-debugging
Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
isuzu-unity-cli
Control Unity Editor from the CLI with the isuzu-unity-cli command. Execute C# code, browse scene hierarchy, inspect/modify GameObjects, capture screenshots, read console logs, check compile status, control play mode, and execute menu items. Use when: user wants to interact with Unity Editor programmatically, run C#…
docs-release-notes
Use when a change needs a user-visible release-note, changelog, or changeset entry — "add a release note", "add a changeset for this", "what goes in the changelog?", "write up what shipped", "note this for the next release" — or when finalizing a branch whose customer-visible features, bug fixes, or UI changes should…