incident-runbooks

incident-runbooks is a skill for Claude Code from alivirgo/Major-AI-Skills. It costs 26 tokens per session (784 once invoked), scanned A, original, MIT.

A guide for writing incident runbooks: short instructions that help an on-call engineer diagnose and respond to a service problem. It organizes symptoms, severity, checks, mitigation, escalation, and follow-up links.

In plain words
What is it for?
Use it to create or review runbooks for alerts, outages, service failures, production rollbacks, and handoffs to other teams.
Why use it?
It turns scattered operational knowledge into clear steps that can be followed under pressure, while reducing unsafe or irreversible actions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Codex.

Part of the major-ai-skills plugin — 147 skills, 8 plugins shipped together

Good fit Use it to create or review runbooks for alerts, outages, service failures, production rollbacks, and handoffs to other teams.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alivirgo/major-ai-skills/incident-runbooks
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 alivirgo/Major-AI-Skills --skill incident-runbooks
Clone the repo
git clone --depth 1 https://github.com/alivirgo/Major-AI-Skills

Made for: Claude Code.

Or install major-ai-skills, the plugin that ships this one along with the rest of its 147 skills, 8 plugins.

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 incident-runbooks

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/alivirgo/major-ai-skills/incident-runbooks"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/incident-runbooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 784 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00026 $0.00784
Opus 5 $0.00013 $0.00392
Sonnet 5 $0.00005 $0.00157
Haiku 4.5 $0.00003 $0.00078

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

Security

Grade A, and why

incident-runbooks 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 yesterday.

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.

skills/incident-runbooks/SKILL.md · 106 lines

How it starts

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

Incident Runbooks AI Skill Guide

Overview & Engine Architecture

An incident runbook is a short, actionable guide an oncall engineer follows under pressure. Good runbooks start from observable symptoms, list safe diagnostics, then mitigation and escalation - not essays. Agents write runbooks that link to dashboards and feature flags, avoid secret values, and keep steps numbered and reversible when possible.

Alert / user report
   -> Symptom match in runbook index
       -> Severity + impact
           -> Diagnose (read-only first)
               -> Mitigate / roll back
                   -> Escalate + handoff notes
                       -> Post-incident follow-ups

When to use this skill

  • Authoring oncall docs for services you own
  • Converting tribal knowledge into page-ready steps
  • Reviewing runbooks for actionability before a launch
  • Linking alerts to the correct playbook URL

Operational directives

  1. Title with the symptom or alert name humans will search (Checkout 5xx elevated).
  2. First section: impact, severity hints, and owners/escalation path.
  3. Prefer read-only diagnostics before mutating production.
  4. Every destructive or customer-facing step needs an explicit confirmation checkpoint.
  5. Never embed passwords, tokens, or private URLs that bypass SSO without vault references.

Runbook template

# Runbook: <Alert or symptom>

## Severity cheat sheet
- SEV1: ...
- SEV2: ...

## Symptoms
- Dashboard: <link>  Panel: ...
- User-visible: ...

## Quick checks (read-only)
1. ...
2. ...

## Mitigation
1. ...
2. Rollback flag/command: ...
3. Verify recovery: ...

## Escalation
- Primary: @team-oncall
- Secondary: @platform
- External vendor: ...

## Do not
- ...

## Follow-ups
- Ticket template / postmortem link

Quality bar

Weak Strong
"Check the logs" Exact query, index, and time window
"Restart if needed" When restart is safe; order of instances; blast radius
"Ask Bob" Role rotation + paging policy
Secret paste in page Link to vault path + access role

Read the full file on GitHub · 106 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. yesterday Changed · -5 tokens per session f8caf8ab5a93
  2. 7d ago First seen · 106 lines · 31 tokens per session scan A 2990dc1c9ecf

Subscribe to this mod's changes

incident-runbooks is a skill published in the GitHub repository alivirgo/Major-AI-Skills (1 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 784 once invoked, about $0.0001 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-09-05.

Related

Other skills, from other repositories

k8s-incident-triage

Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.

initializ/forge · 41 tokens

azure-pipelines

Expert knowledge for Azure Pipelines development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when securing agents/secrets, configuring YAML builds, migrating from Jenkins…

MicrosoftDocs/Agent-Skills · 116 tokens

azure-local

Expert knowledge for Azure Local development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when planning Azure Local racks/SDN, disconnected clusters, Arc VMs, GPU workloads, or…

MicrosoftDocs/Agent-Skills · 112 tokens

azure-virtual-machines

Expert knowledge for Azure Virtual Machines development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when sizing Azure VMs, tuning HPC/GPU/InfiniBand, encrypting disks/Trusted…

MicrosoftDocs/Agent-Skills · 137 tokens

azure-arc

Expert knowledge for Azure Arc development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when managing Arc-enabled Kubernetes, data services, Edge Volumes, Agentic Retrieval APIs…

MicrosoftDocs/Agent-Skills · 114 tokens

azure-blob-storage

Expert knowledge for Azure Blob Storage development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Blob tiers, lifecycle/immutability, NFS/SFTP mounts, static sites, or SDK/CLI data workflows, and…

MicrosoftDocs/Agent-Skills · 112 tokens