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 hoangatg/ai-agent-toolkit --skill incident-respondergit clone --depth 1 https://github.com/hoangatg/ai-agent-toolkitWrote 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/hoangatg/ai-agent-toolkit/incident-responder)<a href="https://agentmods.dev/skills/hoangatg/ai-agent-toolkit/incident-responder"><img src="https://agentmods.dev/badge/skills/hoangatg/ai-agent-toolkit/incident-responder/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/hoangatg/ai-agent-toolkit/incident-responder"><img src="https://agentmods.dev/badge/skills/hoangatg/ai-agent-toolkit/incident-responder.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.00714 |
| Opus 5 | $0.00016 | $0.00357 |
| Sonnet 5 | $0.00006 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
incident-responder 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 6d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Responder
Stay calm. Communicate clearly. Fix it. Learn from it.
1. Incident Lifecycle
Detect → Triage → Mitigate → Resolve → Postmortem → Improve
2. Severity Classification
| Severity | Impact | Response Time | Communication |
|---|---|---|---|
| SEV-1 | Service down, data loss | Immediate (24/7) | Exec + all stakeholders |
| SEV-2 | Major degradation | < 30 min | Team leads |
| SEV-3 | Minor impact | Business hours | Team channel |
| SEV-4 | Cosmetic / low impact | Next sprint | Ticket |
3. Incident Roles
| Role | Responsibility |
|---|---|
| Incident Commander | Coordinates response, makes decisions |
| Technical Lead | Investigates and fixes |
| Communications | Updates stakeholders |
| Scribe | Documents timeline and actions |
4. Response Principles
| Principle | Application |
|---|---|
| Mitigate first | Stop bleeding before root cause |
| Communicate early | Status page update within 5 min |
| Time-box investigation | If no progress in 30 min, escalate |
| Rollback is valid | Revert is faster than forward-fix |
| Document as you go | Timeline of actions and findings |
5. Runbook Template
| Section | Content |
|---|---|
| Symptom | What the alert/report looks like |
| Impact | Who is affected, how badly |
| Quick checks | Dashboard URLs, common causes |
| Mitigation steps | Ordered actions to reduce impact |
| Escalation | Who to contact, when |
| Resolution | Steps to permanently fix |
6. Blameless Postmortem
Structure
| Section | Focus |
|---|---|
| Summary | What happened in 2-3 sentences |
| Impact | Duration, affected users, revenue impact |
| Timeline | Minute-by-minute events |
| Root cause | Why it happened (5 Whys) |
| What went well | Things that worked |
| What went wrong | Things that didn't |
| Action items | Specific, assigned, deadlined |
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.
- 6d ago First seen · 103 lines · 32 tokens per session scan A 63cd8d54857b
incident-responder is a skill published in the GitHub repository hoangatg/ai-agent-toolkit (1 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 714 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-09-03.
Other skills, from other repositories
opencode
Delegate coding tasks to the OpenCode CLI for feature work, refactoring, PR review, and autonomous-style runs. Requires opencode installed where the agent can execute shell commands.
codex
Delegate coding tasks to the OpenAI Codex CLI for features, refactoring, PR reviews, and batch fixes. Requires the codex CLI and typically a git repository.
deepnote
DeepNote knowledge base: persistent interlinked markdown wiki with ingest, query, lint, link graph and history.
golang-patterns
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.
clickhouse-io
ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.