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 nik-kale/sre-skills --skill incident-responsegit clone --depth 1 https://github.com/nik-kale/sre-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/nik-kale/sre-skills/incident-response)<a href="https://agentmods.dev/skills/nik-kale/sre-skills/incident-response"><img src="https://agentmods.dev/badge/skills/nik-kale/sre-skills/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.
<a href="https://agentmods.dev/skills/nik-kale/sre-skills/incident-response"><img src="https://agentmods.dev/badge/skills/nik-kale/sre-skills/incident-response.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.00053 | $0.01554 |
| Opus 5.5 | $0.00021 | $0.00622 |
| Sonnet 5.5 | $0.00011 | $0.00311 |
| Haiku 4.5 | $0.00005 | $0.00155 |
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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response
Systematic framework for investigating and resolving production incidents.
When to Use This Skill
- Production alert firing
- Service outage or degradation reported
- Error rates spiking
- User-reported issues affecting production
- On-call escalation received
Initial Triage (First 5 Minutes)
Copy and track progress:
Incident Triage:
- [ ] Confirm the incident is real (not false positive)
- [ ] Identify affected service(s)
- [ ] Assess severity level
- [ ] Start incident channel/thread
- [ ] Page additional responders if needed
Severity Assessment
Quickly determine severity to guide response urgency:
| Severity | Criteria | Response Time |
|---|---|---|
| SEV1 | Complete outage, data loss risk, security breach | Immediate, all hands |
| SEV2 | Major degradation, significant user impact | < 15 min, primary on-call |
| SEV3 | Partial degradation, limited user impact | < 1 hour |
| SEV4 | Minor issue, workaround available | Next business day |
For detailed severity definitions, see references/severity-levels.md.
Data Gathering
Collect evidence systematically. Don't jump to conclusions.
1. Timeline Construction
Timeline:
- [TIME] First alert/report
- [TIME] ...
- [TIME] Current status
2. Key Data Sources
Metrics - Check in this order:
- Error rates (5xx, exceptions)
- Latency (p50, p95, p99)
- Traffic volume (requests/sec)
- Resource utilization (CPU, memory, disk, connections)
- Dependency health
Logs - Search for:
# Error patterns
level:error OR level:fatal
exception OR panic OR crash
# Correlation
trace_id:<id> OR request_id:<id>
Traces - Find:
- Slowest traces in affected timeframe
- Error traces
- Traces crossing service boundaries
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.
- 2mo ago First seen · 283 lines · 53 tokens per session scan A b5aa82b4ea31
incident-response is a skill published in the GitHub repository nik-kale/sre-skills (12 stars, last pushed 9mo ago), licensed MIT. It adds 53 tokens to every session and 1,554 once invoked, about $0.0002 per session on Opus 5.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-31.
incident-response compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| incident-responsenik-kale/sre-skills | Skill | 12 | 9mo ago | MIT | A | 53 | Claude Code, Codex |
| systematic-debuggingopen-metadata/OpenMetadata | Skill | 16k | yesterday | Apache-2.0 | A | 37 | Claude Code |
| log-error-digestzebbern/claude-code-guide | Skill | 4.7k | 3d ago | MIT | A | 71 | Claude Code, Codex |
| cwv-optimizeradobe/skills | Skill | 319 | yesterday | Apache-2.0 | A | 112 | Claude Code |
| ci-fixersipyourdrink-ltd/bernstein | Skill | 1.2k | yesterday | Apache-2.0 | A | 15 | Claude Code, Codex |
| incident-response-incident-responsermyndharis/antigravity-skills | Skill | 1.9k | 23d ago | MIT | A | 36 | Claude Code |
| triaging-web-analytics-supportPostHog/posthog | Skill | 41k | yesterday | none | A | 151 | Claude Code, Codex |