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/manusco/resonance/incidentnpx skills add manusco/resonance --skill incidentgit clone --depth 1 https://github.com/manusco/resonanceWrote 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/manusco/resonance/incident)<a href="https://agentmods.dev/skills/manusco/resonance/incident"><img src="https://agentmods.dev/badge/skills/manusco/resonance/incident.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.1 | $0.00078 | $0.01943 |
| Opus 5 | $0.00039 | $0.00971 |
| Sonnet 5 | $0.00016 | $0.00389 |
| Haiku 4.5 | $0.00008 | $0.00194 |
Grade A, and why
resonance-ops-incident 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 6d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-ops-incident: stop the bleeding first, learn second
Role: the Incident Commander (IC). Invoked as:
/incident(to run a live production incident). Input: A live signal that production is degraded or down: a page, an alert, an error/latency spike, or a user report you have confirmed. Output: A mitigated and verified system, a captured incident timeline, and a drafted blameless postmortem with owned action items. Definition of Done: The incident is mitigated and recovery is verified against a real signal (not a hunch). A single IC owned the response. The timeline is captured from detection to resolution. A blameless postmortem is drafted: 5-whys on contributing factors, action items each with a named owner, no person blamed. Stakeholders were told it is resolved.
Iron Law: Mitigate before you diagnose. While users are down, your job is to stop the bleeding, not to find the elegant root cause. Roll back or flip the feature flag first. The investigation happens after the graph is green. A beautiful RCA delivered an hour late is a failure.
This procedure has real side effects. Do not auto-fire it. A human declares the incident and stays in the loop for every irreversible action (rollback, flag flip, external status update).
Prerequisites (fail fast)
- The signal is real and confirmed, not a single flaky alert. If you cannot confirm impact (a graph, a reproduced error, a second corroborating report), your first act is to confirm it, then continue.
- You know which surface is affected and roughly how many users. If not, triage (step 1) establishes it before you declare severity.
- You can reach the levers to mitigate: deploy/rollback access, feature-flag console, or the owner who has them. If you cannot, escalating to someone who can is step 3.
Algorithm
Copy this checklist and tick items as you go. Do not skip a step to save time while users are down; skipping mitigation to hunt the root cause is the classic failure this skill exists to prevent.
What ships with it
7 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.
- 6d ago First seen · 77 lines · 78 tokens per session scan A 7731e4de51b1
resonance-ops-incident is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 2d ago), licensed MIT. It adds 78 tokens to every session and 1,943 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…