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/thiientv/godmode/incident-responsenpx skills add thiientv/godmode --skill incident-responsegit clone --depth 1 https://github.com/thiientv/godmodeWrote 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/thiientv/godmode/incident-response)<a href="https://agentmods.dev/skills/thiientv/godmode/incident-response"><img src="https://agentmods.dev/badge/skills/thiientv/godmode/incident-response.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.00082 | $0.00489 |
| Opus 5 | $0.00041 | $0.00244 |
| Sonnet 5 | $0.00016 | $0.00098 |
| Haiku 4.5 | $0.00008 | $0.00049 |
Grade A, and why
incident-response 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.
What it actually says
Incident Response
Stabilize first, learn second. Do not let diagnosis delay a safe reversible mitigation.
Establish control
Record start time, incident commander, responders, severity, affected users and regions, known symptoms, recent changes, communication channel, and next update time. Use incident-record.md as the live log. Separate confirmed facts from hypotheses.
Contain and recover
- Protect people, data integrity, credentials, and irreversible state.
- Reduce blast radius with a kill switch, traffic shift, dependency isolation, rollback, rate limit, or safe degradation when authorized.
- Preserve timestamps, deploy identifiers, logs, metrics, traces, and commands before ephemeral evidence disappears.
- Test ranked hypotheses without making several uncontrolled production changes at once.
- Verify recovery from user-facing behavior and service-level signals, not one green dashboard.
Use release-engineering for a failed rollout, security-and-hardening for an
active security boundary, and root-cause-debugging for deeper diagnosis after
the service is stable. Production mutations require the repository's normal
authority and approval; this skill does not grant it.
Communicate and close
Publish concise updates with verified impact, current mitigation, user action if any, and next update time. Avoid speculative root causes. Close the incident only after critical paths, backlog recovery, data reconciliation, and alert state are checked.
Create a blameless timeline and a small set of owned, dated actions: regression proof, detection gap, recovery improvement, and prevention at the correct owner boundary. Track them outside the incident document.
Completion condition
Impact has ended, recovery is independently verified, data and queued work are reconciled or explicitly owned, communications are complete, and follow-up actions have owners and due dates.
What ships with it
2 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 · 57 lines · 82 tokens per session scan A 8326d936435b
incident-response is a skill published in the GitHub repository thiientv/godmode (93 stars, last pushed 10d ago), licensed MIT. It adds 82 tokens to every session and 489 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
agent-evaluation-v2
Agent Evaluation workflow skill. Use this skill when the user needs Testing and benchmarking LLM agents including behavioral testing, and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
agent-evaluation
Agent Evaluation workflow skill. Use this skill when the user needs Testing and benchmarking LLM agents including behavioral testing, and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
agent-evaluation-v3
Agent Evaluation workflow skill. Use this skill when the user needs Testing and benchmarking LLM agents including behavioral testing, and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…