ai-incident-response

ai-incident-response is a skill for Claude Code from obielin/responsible-ai-skills. It costs 40 tokens per session (1,871 once invoked), scanned A, original, MIT.

A procedure for responding to incidents involving artificial-intelligence systems, such as harmful output, biased behaviour, data exposure, attacks, or major performance decline.

In plain words
What is it for?
Use it to triage AI-related incidents, classify them, decide whether emergency action or regulatory notification may be needed, and guide follow-up.
Why use it?
It gives teams an ordered way to assess urgency, user impact, sensitive data, and incident type before deciding how to respond or escalate.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the responsible-ai-skills plugin — 9 skills shipped together

Good fit Use it to triage AI-related incidents, classify them, decide whether emergency action or regulatory notification may be needed, and guide follow-up.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/obielin/responsible-ai-skills/ai-incident-response
Install

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.

Any agent
npx skills add obielin/responsible-ai-skills --skill ai-incident-response
Clone the repo
git clone --depth 1 https://github.com/obielin/responsible-ai-skills

Made for: Claude Code.

Or install responsible-ai-skills, the plugin that ships this one along with the rest of its 9 skills.

Wrote 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.

agentmods badge for ai-incident-response

README.md
[![agentmods](https://agentmods.dev/badge/skills/obielin/responsible-ai-skills/ai-incident-response/github.svg)](https://agentmods.dev/skills/obielin/responsible-ai-skills/ai-incident-response)
Your own site
<a href="https://agentmods.dev/skills/obielin/responsible-ai-skills/ai-incident-response"><img src="https://agentmods.dev/badge/skills/obielin/responsible-ai-skills/ai-incident-response/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.

agentmods 80×15 button for ai-incident-response

Your own site · 80×15
<a href="https://agentmods.dev/skills/obielin/responsible-ai-skills/ai-incident-response"><img src="https://agentmods.dev/badge/skills/obielin/responsible-ai-skills/ai-incident-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,871 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.01871
Opus 5 $0.00020 $0.00936
Sonnet 5 $0.00008 $0.00374
Haiku 4.5 $0.00004 $0.00187

Measured 12d ago against content hash c197daa2431e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

ai-incident-response scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -f https://your-ai-endpoint/health && echo "STILL RUNNING - escalate" || echo "System stopped"
skills/ai-incident-response/SKILL.md · 286 lines

How it starts

The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AI Incident Response

An AI incident is any event where an AI system's behaviour deviates from its intended, safe, and fair operation. Do not minimise, ignore, or quietly fix these. Follow this process every time.

Immediate Triage (First 15 Minutes)

1. Stop and Assess

Before doing anything else, answer these questions:

Is the system currently causing or about to cause active harm?
  YES → Immediately escalate to P1. Skip to EMERGENCY SHUTDOWN.
  NO  → Continue triage.

Is the incident affecting real citizens / users right now?
  YES → Treat as P1 or P2.
  NO  → Continue triage.

Is personal or sensitive data involved?
  YES → ICO notification may be required within 72 hours.
  NO  → Continue triage.

2. Classify the Incident

Type Examples
Performance degradation Accuracy drops significantly, response times increase
Fairness violation Metrics show disproportionate impact on a group
Safety failure Harmful, dangerous, or illegal output generated
Data incident Unauthorised access, accidental disclosure, data poisoning
Manipulation Prompt injection, adversarial attack, model inversion
Compliance failure GDPR breach, ATRS not updated, override log missing

3. Assign Severity

P1 — Critical: System actively causing harm. Shut down immediately.
P2 — High:     Significant risk of harm. Pause within 4 hours.
P3 — Medium:   Fairness or performance threshold exceeded. Fix within 24 hours.
P4 — Low:      Anomaly detected. Investigate within 72 hours.

Emergency Shutdown (P1 Only)

Execute this in order. Do not skip steps.

# Step 1: Stop new requests immediately
# (Replace with your actual shutdown command)
systemctl stop ai-inference-service
# or: kubectl scale deployment ai-service --replicas=0
# or: disable the API gateway route

# Step 2: Verify the system is stopped
curl -f https://your-ai-endpoint/health && echo "STILL RUNNING - escalate" || echo "System stopped"

# Step 3: Preserve all logs — do NOT rotate or delete
cp -r /var/log/ai-service/ /var/log/ai-service-incident-backup-$(date +%Y%m%d%H%M%S)/

# Step 4: Activate manual fallback
# (Document your manual fallback procedure here)
echo "Activating manual fallback process — notify [team lead name]"

# Step 5: Notify emergency contacts immediately
# (Add your actual contacts)

Read the full file on GitHub · 286 lines

Changes

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.

  1. 12d ago First seen · 286 lines · 40 tokens per session scan A c197daa2431e

Subscribe to this mod's changes

ai-incident-response is a skill published in the GitHub repository obielin/responsible-ai-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 1,871 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

ddia-principles

Designing Data-Intensive Applications (DDIA) distilled reference guide by Martin Kleppmann. MUST be loaded when: designing database schemas, choosing storage engines, implementing replication or partitioning, handling distributed transactions, building batch/stream processing pipelines, choosing consistency models…

satbirbhbc-ux/ai-coding-principles · 185 tokens

ai-coding-discipline

Mandatory coding discipline rules that prevent common AI coding anti-patterns. MUST be loaded for ALL code writing, editing, reviewing, bug fixing, and testing tasks. Trigger on: writing code, editing code, fixing bugs, writing tests, implementing features, refactoring, code review, creating functions, adding error…

satbirbhbc-ux/ai-coding-principles · 100 tokens

extract

Run the full Semantica semantic extraction pipeline on a file or selected text — NER, relations, events, coreference resolution, triplets, and validation. Clears result cache before each run. Returns Markdown tables with entity/relation/event/triplet results and inline validator warnings.

semantica-agi/semantica · 59 tokens

dd-synthesis

Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.

Abilityai/trinity · 33 tokens

loop-orchestration

Reference loop-orchestration example; a local loop host chains governed runx turns through receipts, budgets, context, and stop policy.

runxhq/runx · 32 tokens

loop-operator-context

Advisory operating context for the loop-orchestration example.

runxhq/runx · 18 tokens