ai-sre-incident-response

ai-sre-incident-response is a skill for Claude Code from lingxling/awesome-skills-cn. It costs 32 tokens per session (2,946 once invoked), scanned A, a copy of ai-sre-incident-response, MIT.

An incident-response playbook for AI services, including language-model outages, poor answers, unsafe outputs, high usage costs, and provider failures.

In plain words
What is it for?
Use it to define incident severity, monitor latency, errors, cost, and quality, coordinate on-call response, and fail over or roll back model and prompt changes.
Why use it?
It gives responders a way to classify AI-specific failures and handle quality, safety, availability, and spending problems with monitoring and rollback practices.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the agentic-awesome-skills plugin — 174 skills shipped together

Good fit Use it to define incident severity, monitor latency, errors, cost, and quality, coordinate on-call response, and fail over or roll back model and prompt changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lingxling/awesome-skills-cn/ai-sre-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 lingxling/awesome-skills-cn --skill ai-sre-incident-response
Clone the repo
git clone --depth 1 https://github.com/lingxling/awesome-skills-cn

Made for: Claude Code.

Or install agentic-awesome-skills, the plugin that ships this one along with the rest of its 174 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-sre-incident-response

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/lingxling/awesome-skills-cn/ai-sre-incident-response"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/ai-sre-incident-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,946 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 100% copy Near-identical to another mod 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.00032 $0.02946
Opus 5.5 $0.00013 $0.01178
Sonnet 5.5 $0.00006 $0.00589
Haiku 4.5 $0.00003 $0.00295

Measured 13d ago against content hash b9654a5db9e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ai-sre-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 13d 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 -s -o /dev/null -w "%{http_code}" https://api.provider.com/health
Origin

This is a copy

100% identical to ai-sre-incident-response — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

antigravity-awesome-skills/plugins/agentic-awesome-skills-claude/skills/ai-sre-incident-response/SKILL.md · 337 lines

How it starts

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

AI SRE Incident Response

Apply SRE rigor to AI systems where incidents include quality regressions, unsafe outputs, and budget explosions.

When to Use This Skill

  • An LLM endpoint begins returning degraded or hallucinated answers
  • Token spend spikes beyond budget thresholds
  • A model provider goes down and traffic must fail over
  • Safety guardrails fire at abnormal rates
  • A new model deployment causes latency or accuracy regression

Prerequisites

  • Prometheus and Alertmanager deployed with scrape targets for AI services
  • Grafana dashboards for golden signals (latency, error rate, cost, quality)
  • On-call rotation configured in PagerDuty, Opsgenie, or equivalent
  • Runbook repository accessible to responders
  • Rollback mechanism for model and prompt versions (GitOps or feature flags)

AI Incident Classes

  • Availability incident: model/provider unavailable, timeout storm.
  • Quality incident: answer accuracy or tool success drops below SLO.
  • Safety incident: harmful or policy-violating outputs increase.
  • Cost incident: unexpected token or provider spend spike.

Severity Framework

Severity Criteria Response Time Notification
SEV1 User-facing outage, compliance risk, data leak 5 min Page on-call + incident commander
SEV2 Major degradation in key flows 15 min Page on-call
SEV3 Limited impact or internal-only issue 1 hour Slack alert
SEV4 Cosmetic or low-priority regression Next business day Ticket

Golden Signals for AI Services

  • Request success rate
  • Latency (queue + generation + tool execution)
  • Hallucination/groundedness proxy metrics
  • Cost per minute and per tenant
  • Guardrail violation rate

Prometheus Alert Rules

# prometheus-ai-alerts.yaml
groups:
  - name: ai-service-alerts
    rules:
      - alert: ModelEndpointDown
        expr: up{job="llm-inference"} == 0
        for: 2m
        labels:
          severity: sev1
        annotations:
          summary: "LLM inference endpoint {{ $labels.instance }} is down"
          runbook_url: "https://runbooks.internal/ai/model-outage"

      - alert: HighHallucinationRate
        expr: |
          rate(llm_hallucination_detected_total[10m])
          / rate(llm_requests_total[10m]) > 0.15
        for: 5m
        labels:
          severity: sev2
        annotations:
          summary: "Hallucination rate above 15% for {{ $labels.model }}"
          runbook_url: "https://runbooks.internal/ai/quality-regression"

      - alert: TokenCostExplosion
        expr: |
          sum(rate(llm_token_cost_dollars[5m])) by (tenant)
          > 0.50
        for: 3m
        labels:
          severity: sev2
        annotations:
          summary: "Token spend exceeds $0.50/min for tenant {{ $labels.tenant }}"
          runbook_url: "https://runbooks.internal/ai/cost-spike"

      - alert: LatencyP95Exceeded
        expr: |
          histogram_quantile(0.95,
            rate(llm_request_duration_seconds_bucket[5m])
          ) > 5
        for: 5m
        labels:
          severity: sev2
        annotations:
          summary: "LLM p95 latency exceeds 5s for {{ $labels.service }}"

      - alert: GuardrailViolationSpike
        expr: |
          rate(llm_guardrail_violations_total[10m])
          / rate(llm_requests_total[10m]) > 0.05
        for: 5m
        labels:
          severity: sev1
        annotations:
          summary: "Guardrail violations above 5% for {{ $labels.model }}"
          runbook_url: "https://runbooks.internal/ai/safety-incident"

      - alert: ModelQualityDrop
        expr: |
          llm_eval_score{metric="groundedness"} < 0.70
        for: 10m
        labels:
          severity: sev2
        annotations:
          summary: "Groundedness score dropped below 0.70 for {{ $labels.model }}"

      - alert: ProviderErrorRateHigh
        expr: |
          rate(llm_provider_errors_total[5m])
          / rate(llm_provider_requests_total[5m]) > 0.10
        for: 3m
        labels:
          severity: sev2
        annotations:
          summary: "Provider {{ $labels.provider }} error rate above 10%"

Read the full file on GitHub · 337 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. 13d ago First seen · 337 lines · 32 tokens per session scan A b9654a5db9e0

Subscribe to this mod's changes

ai-sre-incident-response is a skill published in the GitHub repository lingxling/awesome-skills-cn (314 stars, last pushed 13d ago), licensed MIT. It adds 32 tokens to every session and 2,946 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to ai-sre-incident-response, differing in 25 lines, and is treated as a copy.

Related

Other skills, from other repositories

mm-doctor

A diagnostic workflow for checking the health of the mm system, including its configuration, project links, note vault, passports, session archive, and planning consistency.

mworldorg/markdown-memory · 126 tokens

inversion

"Invert, always invert." Apply Carl Jacobi's mathematical principle and Charlie Munger's investing wisdom to solve problems by thinking backward from failure. Use when: Goal setting - Define what would guarantee failure, then avoid it; Risk analysis - Identify what could destroy your project before starting; Decision…

guia-matthieu/clawfu-skills · 96 tokens

deliverability-checker

Check email deliverability and DNS configuration. Use when: diagnosing email delivery issues; setting up new email domains; auditing email authentication; checking SPF/DKIM/DMARC; troubleshooting spam folder issues.

guia-matthieu/clawfu-skills · 44 tokens

rlm

Process large codebases (>100 files) using the Recursive Language Model pattern. Orchestrates parallel sub-agents to map-reduce across files without context rot. Use when: analyzing large repositories; auditing security or auth across many files; finding patterns across 50+ files; processing large log files or data…

guia-matthieu/clawfu-skills · 65 tokens

link-checker

Find broken links on websites. Use when: auditing website for broken links; checking internal link structure; finding 404 errors; validating external links; pre-launch QA.

guia-matthieu/clawfu-skills · 36 tokens

performance-optimization

Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.

addyosmani/agent-skills · 59 tokens