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 agentmods add skills/cyperx84/claude-code-plugin-examples/incident-responsenpx skills add cyperx84/claude-code-plugin-examples --skill incident-responsegit clone --depth 1 https://github.com/cyperx84/claude-code-plugin-examplesWrote 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/cyperx84/claude-code-plugin-examples/incident-response)<a href="https://agentmods.dev/skills/cyperx84/claude-code-plugin-examples/incident-response"><img src="https://agentmods.dev/badge/skills/cyperx84/claude-code-plugin-examples/incident-response.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.03180 |
| Opus 5 | $0.00010 | $0.01590 |
| Sonnet 5 | $0.00004 | $0.00636 |
| Haiku 4.5 | $0.00002 | $0.00318 |
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 3d 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 — 593 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response
Purpose
Effective incident response through:
- Rapid incident detection
- Structured response process
- Clear communication
- Root cause analysis
- Prevention strategies
When to Use
Invoke this skill when:
- Production outage occurs
- Performance degradation detected
- Security incident suspected
- Preparing incident runbooks
- Conducting post-mortems
Incident Response Framework
Incident Severity Levels
SEV 1 (Critical):
- Complete service outage
- Data loss/corruption
- Security breach
- Revenue impact: High
Response Time: Immediate
Team: Full on-call rotation
SEV 2 (High):
- Partial service degradation
- Major feature broken
- Affecting multiple customers
- Revenue impact: Medium
Response Time: <15 minutes
Team: Primary on-call + specialist
SEV 3 (Medium):
- Minor feature issue
- Affecting some users
- Workaround available
- Revenue impact: Low
Response Time: <1 hour
Team: Primary on-call
SEV 4 (Low):
- Cosmetic issues
- Single user affected
- No revenue impact
Response Time: Next business day
Team: During business hours
Incident Response Process
1. Detection (Minutes 0-5)
How Incidents Are Detected:
- Automated alerts (monitoring)
- User reports (support tickets)
- Social media mentions
- Team members noticing issues
- Deployment gone wrong
Initial Assessment:
interface Incident {
severity: 'SEV1' | 'SEV2' | 'SEV3' | 'SEV4';
description: string;
affectedSystems: string[];
userImpact: string;
startTime: Date;
}
function assessIncident(alert: Alert): Incident {
// Determine severity
const severity = calculateSeverity({
usersAffected: alert.affectedUsers,
systemsDown: alert.failingSystems,
revenueImpact: alert.estimatedRevenueLoss,
});
return {
severity,
description: alert.message,
affectedSystems: alert.systems,
userImpact: estimateUserImpact(alert),
startTime: new Date(),
};
}
2. Response (Minutes 5-10)
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.
- 3d ago First seen · 593 lines · 20 tokens per session scan A 93c3b06f0b86
Incident Response is a skill published in the GitHub repository cyperx84/claude-code-plugin-examples (2 stars, last pushed 10mo ago), licensed MIT. It adds 20 tokens to every session and 3,180 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…