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 saemihemma/lead-producer-oss --skill workflow-incident-responsegit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/workflow-incident-response)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/workflow-incident-response"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-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/saemihemma/lead-producer-oss/workflow-incident-response"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-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.00039 | $0.00943 |
| Opus 5.5 | $0.00016 | $0.00377 |
| Sonnet 5.5 | $0.00008 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
workflow-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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response Workflow
Purpose
Structured process for production incidents. Turns chaos into a sequence: detect → triage → act → verify → learn. Produces a durable incident report artifact.
Use When
- Live production incident (service down, exploit active, economy anomaly, data corruption)
- Post-incident: need to document what happened and prevent recurrence
- Pre-launch: rehearsing incident response readiness
Do NOT Use When
- Bug investigation in development (use
workflow-systematic-debugging) - Proactive security review (use
team-red-team) - Infrastructure design (use
team-infrastructure) - Issue is already resolved and just needs documentation
Roles Involved
- role-liveops-engineer: owns triage, severity, player-impact, action decision
- role-devops-engineer: owns deployment, rollback execution, monitoring
- role-security-engineer: joins if exploit or abuse is involved
- role-analytics-engineer: joins if metrics anomaly or data integrity is involved
- role-community-developer: owns player communication if impact is player-visible
Workflow
Phase 1: Detect & Classify
- Confirm the incident is real (not false alarm or monitoring artifact).
- Classify severity using LiveOps Engineer's framework: critical / high / medium / low.
- Determine trend: getting worse, stable, or self-resolving.
- Identify blast radius from LiveOps triage: which systems, how many players, which regions.
Phase 2: Triage & Decide
- LiveOps Engineer assesses options: hotfix, rollback, degrade, monitor.
- For on-chain incidents: check contract state, pause mechanisms, off-chain mitigation.
- Choose action. LiveOps must specify rollback plan if the fix itself fails.
- If severity is critical and action is irreversible, escalate to user before executing.
- If "monitor" is chosen, define the escalation trigger (metric, threshold, timeframe). If trigger fires, return to step 2 for re-triage.
Phase 3: Act & Verify
- DevOps executes chosen action.
- Verify fix: confirm the specific failure signal has stopped.
- Monitor for secondary effects (did the fix break something else?).
- If fix fails or creates secondary issues: DevOps alerts LiveOps immediately for re-triage (return to step 5 with new information).
- If player-visible: Community Developer acknowledges issue immediately; delays technical explanation until root cause is clear.
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 · 87 lines · 39 tokens per session scan A 025f2487a0b4
workflow-incident-response is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 943 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-31.
Other skills, from other repositories
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
ci-fixer
CI failures - read error, minimal fix, verify.
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…