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 FlyFission/nuclear-grade-context-engineering --skill responding-to-incidentsgit clone --depth 1 https://github.com/FlyFission/nuclear-grade-context-engineeringWrote 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/flyfission/nuclear-grade-context-engineering/responding-to-incidents)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/responding-to-incidents"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/responding-to-incidents/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/flyfission/nuclear-grade-context-engineering/responding-to-incidents"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/responding-to-incidents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.01289 |
| Opus 5 | $0.00040 | $0.00645 |
| Sonnet 5 | $0.00016 | $0.00258 |
| Haiku 4.5 | $0.00008 | $0.00129 |
Grade A, and why
responding-to-incidents 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 10d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Responding to Incidents
Overview
In a casualty you stabilize first and analyze second. An incident is run by one named commander, keeps known facts separate from guesses, prefers reversible moves while the picture is unclear, communicates on a fixed cadence, and does not close until corrective actions are tracked to done. The goal is to stop the harm and preserve the truth of what happened, not to find blame in the moment.
Decision contract
- Claim checked: the incident has one named commander, a timeline that keeps confirmed facts separate from hypotheses, and corrective actions that each carry an owner and a definition of done -- none left as "we should."
- Artifact observed: the current symptom, what changed, who can authorize rollbacks/failovers/comms, and the reversible actions available -> an
incident.md(timeline, facts-vs-hypotheses, decisions, comms), owned corrective actions with closure triggers, and a handoff to learning and deficiency records. - Decision affected: block -- whether the incident is stabilized and its corrective actions are owned with closure triggers (it stays open until then).
- Failure class: premature-incident-close (closed with unowned actions, or a hypothesis recorded as fact).
- Next action: stop a proposed irreversible fix until the cause is confirmed or risk is accepted by a named owner; keep the incident open until actions are owned.
When to Use
- Production is down or degraded, data is at risk, security is in question, or users are harmed.
- An agent took a harmful action, or a release is failing its abort criteria.
- Multiple people or agents need one source of truth and one decision-maker during a live event.
When Not to Use
- The work is routine and reversible with no live harm (use the normal change path).
- The event is over and the task is the lesson, not the response (use
learning-from-experience). - A standing known problem needs logging, not a live response (use
tracking-deficiencies).
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.
- 10d ago First seen · 108 lines · 80 tokens per session scan A c5dd562f90dc
responding-to-incidents is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 1,289 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
deslop
Audit or apply evidence-backed, test-first subtractive cleanup for accumulated agent-created test bloat, verification theater, and defensive or fallback bloat while preserving independent external behavior. Invoke explicitly for semantic simplification, not generic refactoring.
thumbgate-doctor
Health-check whether ThumbGate is actually wired into this agent — PreToolUse/SessionStart hooks installed, MCP server reachable, lesson store present, statusline, and overall agent-readiness — then report exactly what to fix. Runs the existing npx thumbgate doctor audit and the checkoperationalintegrity MCP tool. Use…
prevention-rules
Generate and review prevention rules auto-promoted from repeated failure patterns.
add-plugin
Use when installing, disabling, enabling, or troubleshooting a third-party octomux plugin — the manifest row shape, octomux plugins list/disable/enable, reading octomux doctor output, and recovering a broken boot with --safe-mode.
create-task
Use when creating an octomux task to dispatch autonomous Claude Code agents for building features, fixing bugs, or any code changes.
debugging
Investigate failures whose root cause is still unknown — narrow the search space, instrument, and test falsifiable hypotheses. Use for intermittent or environment-dependent behavior, unexplained stack traces, regressions with no known trigger, or any symptom without a confirmed cause. Ends once the root cause is…