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 omergocmen/vibe-coder-kit --skill incident-responsegit clone --depth 1 https://github.com/omergocmen/vibe-coder-kitWrote 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/omergocmen/vibe-coder-kit/incident-response)<a href="https://agentmods.dev/skills/omergocmen/vibe-coder-kit/incident-response"><img src="https://agentmods.dev/badge/skills/omergocmen/vibe-coder-kit/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/omergocmen/vibe-coder-kit/incident-response"><img src="https://agentmods.dev/badge/skills/omergocmen/vibe-coder-kit/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.00047 | $0.01414 |
| Opus 5.5 | $0.00019 | $0.00566 |
| Sonnet 5.5 | $0.00009 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00141 |
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 1mo 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response Skill
When to Trigger
- Production is down or severely degraded
- Error rate spikes significantly above baseline
- A customer reports a critical bug in production
- A security breach or data leak is suspected
- A deployment caused an unexpected regression
Step-by-Step Process
1. Declare and Classify the Incident
First: breathe. Then classify.
| Severity | Definition | Response Time |
|---|---|---|
| P1 — Critical | Full outage, data loss, security breach | Immediate |
| P2 — High | Major feature broken, significant users affected | < 30 min |
| P3 — Medium | Partial degradation, workaround exists | < 2 hours |
| P4 — Low | Minor bug, cosmetic issue | Next sprint |
Open .agent/incidents/INC-<YYYY-MM-DD>-<slug>.md and write:
# Incident: <short title>
**Date:** <YYYY-MM-DD HH:MM UTC>
**Severity:** P<N>
**Status:** Investigating
**Incident Commander:** <name>
2. Triage — Gather Evidence Fast
Don't guess. Collect data first.
Checklist:
- What is the user-visible symptom?
- When did it start? (check monitoring, not just "someone reported it")
- What changed recently? (last deploy, config change, dependency update)
- What does the error log say? (get exact error messages + stack traces)
- Is it affecting all users or a subset?
- Is there an automated alert, or was this user-reported?
Commands to run immediately:
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.
- 1mo ago First seen · 180 lines · 47 tokens per session scan A 0ee3fc4ce4bc
incident-response is a skill published in the GitHub repository omergocmen/vibe-coder-kit (96 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 1,414 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-30.
Other skills, from other repositories
distributed-tracing
Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.
binary-analysis-patterns
Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing static analysis on binaries.
code-refactoring-context-restore
Restore saved project context, architectural decisions, and work state. Use when resuming interrupted work, retrieving prior context, or merging context across sessions.
debugging-toolkit-smart-debug
Diagnose software failures using observability data, ranked hypotheses, and targeted instrumentation. Use when the cause is unclear or an issue requires systematic investigation.
error-diagnostics-smart-debug
Diagnose software failures using observability data, ranked hypotheses, and targeted instrumentation. Use when the cause is unclear or an issue requires systematic investigation.
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.