Borrowing it
Nothing to install: this file belongs to sourjya/kiro-rails. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sourjya/kiro-rails/main/.claude/skills/incident-response/SKILL.mdgit clone --depth 1 https://github.com/sourjya/kiro-railsWrote 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/sourjya/kiro-rails/incident-response)<a href="https://agentmods.dev/skills/sourjya/kiro-rails/incident-response"><img src="https://agentmods.dev/badge/skills/sourjya/kiro-rails/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/sourjya/kiro-rails/incident-response"><img src="https://agentmods.dev/badge/skills/sourjya/kiro-rails/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.00032 | $0.01074 |
| Opus 5 | $0.00016 | $0.00537 |
| Sonnet 5 | $0.00006 | $0.00215 |
| Haiku 4.5 | $0.00003 | $0.00107 |
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 12d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response Checklist
When a security incident is detected or suspected, follow this structured response. Do NOT improvise - skipping steps destroys evidence or widens the breach.
Phase 1: Immediate Containment (first 15 minutes)
- Confirm the incident - distinguish a real breach from a false alarm. Check: unauthorized access logs, unexpected data exfiltration, credential exposure, malware indicators, customer reports.
- Stop the bleeding - contain without destroying evidence:
- Revoke compromised credentials (API keys, tokens, passwords) - rotate, don't delete
- Block attacker IPs/ranges at WAF or security group level
- Disable compromised user accounts (suspend, don't delete)
- Isolate affected systems (remove from load balancer, restrict network access)
- Preserve evidence BEFORE remediation:
- Snapshot affected EBS volumes, RDS instances, container filesystems
- Export CloudTrail, VPC Flow Logs, application logs for the incident window
- Screenshot or export any attacker-visible artifacts (defacement, unauthorized changes)
- Record timestamps of discovery and each containment action
- Do NOT reboot, redeploy,
git reset, delete logs, or destroy state until evidence is preserved.
Phase 2: Scope Assessment
- Determine blast radius:
- Which systems were accessed? (check auth logs, session records)
- What data was exposed or exfiltrated? (check DB query logs, API access logs, S3 access logs)
- How long was the attacker present? (earliest indicator → containment time)
- Were other accounts/tenants affected? (cross-tenant leakage check)
- Identify the entry point:
- Credential compromise (which credential, how obtained)
- Vulnerability exploitation (which endpoint, which CVE)
- Social engineering / phishing (which user, what access)
- Supply chain (which dependency, which version)
- Document in
docs/security/INCIDENT-{YYYY-MM-DD}.md:- Timeline of events
- Systems affected
- Data potentially exposed
- Entry point and attack vector
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.
- 12d ago First seen · 104 lines · 32 tokens per session scan A df1195166280
incident-response is a skill published in the GitHub repository sourjya/kiro-rails (9 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 1,074 once invoked, about $0.0002 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.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…