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 686f6c61/alfred-dev --skill incident-responsegit clone --depth 1 https://github.com/686f6c61/alfred-devWrote 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/686f6c61/alfred-dev/incident-response)<a href="https://agentmods.dev/skills/686f6c61/alfred-dev/incident-response"><img src="https://agentmods.dev/badge/skills/686f6c61/alfred-dev/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/686f6c61/alfred-dev/incident-response"><img src="https://agentmods.dev/badge/skills/686f6c61/alfred-dev/incident-response.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.01047 |
| Opus 5.5 | $0.00020 | $0.00419 |
| Sonnet 5.5 | $0.00010 | $0.00209 |
| Haiku 4.5 | $0.00005 | $0.00105 |
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 2mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Respuesta ante incidentes
El usuario ha reportado o detectado un incidente en produccion. Sigue este protocolo paso a paso para gestionar la respuesta de forma estructurada, desde el triaje inicial hasta el postmortem final.
Resumen
Los incidentes en produccion requieren una respuesta rapida pero ordenada. La tentacion es saltar directamente al codigo, pero sin un triaje previo se pierde tiempo en diagnosticos erroneos. Este protocolo exige documentar cada paso y registrar las lecciones aprendidas para reducir recurrencias.
Proceso
Fase 1: Triaje (qa-engineer)
Usa la herramienta Agent para lanzar al agente qa-engineer con la siguiente mision:
- Clasificar la severidad del incidente (P0 critico, P1 alto, P2 medio, P3 bajo).
- Identificar el impacto: usuarios afectados, funcionalidad comprometida, datos en riesgo.
- Recopilar evidencia: logs, trazas, capturas, mensajes de error.
- Definir si hay workaround inmediato.
Artefacto: informe de triaje con severidad, impacto y evidencia.
Fase 2: Mitigacion (senior-dev)
Si el triaje indica P0 o P1, ejecutar mitigacion inmediata:
- Aplicar workaround si existe (rollback, feature flag, redirect de trafico).
- Si no hay workaround, desarrollar hotfix minimo con test de regresion.
- Desplegar la mitigacion y verificar que el impacto se reduce.
Artefacto: commit de mitigacion con test de regresion.
Fase 3: Analisis de causa raiz (senior-dev + security-officer)
Una vez mitigado el impacto, investigar la causa raiz:
- Trazar la cadena de eventos desde el trigger hasta el fallo.
- Identificar la causa raiz (no el sintoma).
- Si el incidente tiene componente de seguridad, el security-officer audita la cadena.
- Registrar la causa raiz como decision en la memoria del proyecto.
Artefacto: documento de RCA (Root Cause Analysis).
Fase 4: Postmortem
Generar un informe postmortem completo:
- Cronologia del incidente (cuando se detecto, cuando se mitigo, cuando se resolvio).
- Causa raiz confirmada.
- Acciones correctivas con responsable y fecha limite.
- Acciones preventivas para evitar recurrencia.
- Lecciones aprendidas.
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.
- 2mo ago First seen · 102 lines · 49 tokens per session scan A 4a9112483b0a
incident-response is a skill published in the GitHub repository 686f6c61/alfred-dev (115 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 1,047 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
sdlc-graph-engineering-install
Install graph engineering into a project: take an existing process — skills, a runbook, a README, a CI pipeline, or something the user can only describe out loud — and scaffold it into a working guarded graph with typed nodes, total exit guards, bounded retry loops, a durable run-state file, and a ledger recording…
frontend-design
A guide to building polished web interfaces, including their layout, colors, typography, responsive behavior, and interactive states.
research
A research workflow for investigating a question using multiple sources and producing a cited Markdown report under docs/research/.
architecture
A guide for making high-level software architecture decisions, such as choosing system patterns, databases, and ways to handle growth.
brainstorm
A guided conversation for turning a vague creative idea into a clear proposal. It asks one question at a time and checks what you want, who it is for, how success will be measured, and what limits apply.
oss-strategy
Evaluate an open-source business and community strategy. Triggers on "open source strategy", "OSS 策略".