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 pratikxpanda/agentskills-sdk --skill incident-responsegit clone --depth 1 https://github.com/pratikxpanda/agentskills-sdkWrote 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/pratikxpanda/agentskills-sdk/incident-response)<a href="https://agentmods.dev/skills/pratikxpanda/agentskills-sdk/incident-response"><img src="https://agentmods.dev/badge/skills/pratikxpanda/agentskills-sdk/incident-response.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00606 |
| Opus 5 | $0.00013 | $0.00303 |
| Sonnet 5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00061 |
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 8d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response
This skill provides structured guidance for handling production incidents.
When to Declare an Incident
An incident should be declared when:
- A production service is degraded or unavailable for users
- Data integrity may be compromised
- A security breach is suspected
- SLA thresholds are at risk of being violated
Roles
| Role | Responsibility |
|---|---|
| Incident Commander (IC) | Owns the incident lifecycle, coordinates response, makes decisions |
| Communications Lead | Keeps stakeholders informed, posts status updates, manages the incident channel |
| Technical Lead | Drives root cause investigation, coordinates engineering fixes |
General Triage Steps
- Acknowledge - Confirm you are responding to the alert
- Assess - Determine severity using the severity-levels reference
- Communicate - Open an incident channel and notify stakeholders
- Escalate - Follow the escalation policy based on severity
- Mitigate - Apply immediate fixes to restore service
- Resolve - Confirm the issue is fully resolved and monitoring is clean
- Postmortem - Schedule and complete a blameless postmortem within 48 hours
Communication Expectations
- Status updates every 15 minutes for SEV1, 30 minutes for SEV2
- All communication happens in the incident Slack channel
- External customer communication is handled by the Communications Lead
- Management is notified per the escalation policy
Available References
severity-levels.md- Severity definitions (SEV1-SEV4) with impact and response timesescalation-policy.md- Who to page per severity level and escalation timelinespostmortem-template.md- Structured template for blameless postmortems
Available Scripts
page-oncall.sh- Page the on-call engineer via PagerDuty APIcreate-incident-channel.sh- Create a dedicated Slack incident channel
Available Assets
escalation-flowchart.mermaid- Visual flowchart of the escalation processseverity-ladder.png- The four severity bands, most severe at the top. Fetch this withget_skill_assetwhen you need to see the ladder rather than read it; on a vision-capable setup it arrives as an image.
What ships with it
8 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.
- assets/escalation-flowchart.mermaid 703 B
- assets/severity-ladder.png 461 B
- evals/triage.yaml 884 B
- references/escalation-policy.md 1.7 KB
- references/postmortem-template.md 1.6 KB
- references/severity-levels.md 1.8 KB
- scripts/create-incident-channel.sh 1.5 KB runs code
- scripts/page-oncall.sh 909 B runs code
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.
- 8d ago First seen · 69 lines · 26 tokens per session scan A 72004614d204
incident-response is a skill published in the GitHub repository pratikxpanda/agentskills-sdk (24 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 606 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…