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 alivirgo/Major-AI-Skills --skill incident-runbooksgit clone --depth 1 https://github.com/alivirgo/Major-AI-SkillsWrote 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/alivirgo/major-ai-skills/incident-runbooks)<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.
<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>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.00026 | $0.00784 |
| Opus 5 | $0.00013 | $0.00392 |
| Sonnet 5 | $0.00005 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
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.
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
- Title with the symptom or alert name humans will search (
Checkout 5xx elevated). - First section: impact, severity hints, and owners/escalation path.
- Prefer read-only diagnostics before mutating production.
- Every destructive or customer-facing step needs an explicit confirmation checkpoint.
- 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 |
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.
- yesterday Changed · -5 tokens per session f8caf8ab5a93
- 7d ago First seen · 106 lines · 31 tokens per session scan A 2990dc1c9ecf
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.
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.
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…
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…
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…
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…
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…