Borrowing it
Nothing to install: this file belongs to hiepdnh/Agentic-Development-Lifecycle. 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/hiepdnh/Agentic-Development-Lifecycle/main/.claude/skills/ops-incident/SKILL.mdgit clone --depth 1 https://github.com/hiepdnh/Agentic-Development-LifecycleWrote 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/hiepdnh/agentic-development-lifecycle/ops-incident)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/ops-incident"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/ops-incident.svg" alt="Measured on agentmods" 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.00075 | $0.00888 |
| Opus 5 | $0.00037 | $0.00444 |
| Sonnet 5 | $0.00015 | $0.00178 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
ops-incident 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 7d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /ops-incident
Role: DevOps / On-call Engineer
Mục đích: Hướng dẫn triage incident, tạo RCA template, document bài học.
Hướng dẫn thực hiện
Bước 1 — Triage nhanh (KHÔNG dừng để hỏi, chạy ngay)
Khi incident xảy ra, triage theo thứ tự:
## INCIDENT TRIAGE
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | IMPACT: Bao nhiêu user/service bị ảnh hưởng? | _(điền vào)_ |
| 2 | SEVERITY | A: P1 — down hoàn toàn / B: P2 — degraded / C: P3 — minor / D: Khác: ___ |
| 3 | STARTED: Lúc nào bắt đầu? | _(điền thời gian)_ |
| 4 | SYMPTOMS: Biểu hiện cụ thể? | _(điền vào)_ |
Bước 2 — Hỗ trợ Investigation
Dựa trên symptoms, đề xuất 3 hướng điều tra song song:
## Incident [INC-XXX] — P[N]
**Impact**: [Mô tả]
**Started**: [Time]
### 3 hướng điều tra ưu tiên:
**Hướng A**: [Giả thuyết 1] — Check: [command/dashboard cụ thể]
**Hướng B**: [Giả thuyết 2] — Check: [...]
**Hướng C**: [Giả thuyết 3] — Check: [...]
Tôi suggest bắt đầu với Hướng A vì [lý do].
Ai sẽ check Hướng nào?
Bước 3 — Tạo RCA Template
Sau khi incident được resolve, tạo docs/reports/INC-[XXX]-RCA.md dùng template templates/incident-report.md.
Điền vào:
- Frontmatter: incidentId, severity (P1-P4), startTime/endTime/durationMinutes, incidentCommander
- Tóm tắt: 2-3 câu — chuyện gì xảy ra, khi nào, ảnh hưởng user
- Ảnh hưởng: số user bị ảnh hưởng, tính năng bị ảnh hưởng, SLA impact, có notify khách JP không
- Timeline: timestamps thực tế từ incident; bao gồm detect → ack → tìm root cause → fix → resolved
- Root Cause: trigger event + phân tích 5 Whys + contributing factors
- Điều tốt / Cần cải thiện: blameless — focus vào hệ thống, không phải con người
- Action Items: tối thiểu AI-001 (prevent recurrence), AI-002 (improve detection), AI-003 (update runbook)
- Tài liệu hỗ trợ: link đến logs, dashboards, PR liên quan
Bước 4 — Gate cuối RCA
RCA draft hoàn thành.
Câu hỏi quan trọng:
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | "5 Whys" — root cause [X] có đúng không? | A: Đúng / B: Còn layer sâu hơn — layer đó là: ___ / C: Khác: ___ |
| 2 | Action Items — AI-001 có realistic trong deadline không? | A: Có / B: Không — cần adjust: ___ / C: Khác: ___ |
| 3 | Có contributing factor nào bị bỏ sót không? | A: Không / B: Có — factor: ___ / C: Khác: ___ |
| 4 | Ai cần review RCA này trước khi share rộng? | _(điền tên)_ |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 82 lines · 75 tokens per session scan A e8fd44db534a
ops-incident is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 10d ago), licensed MIT. It adds 75 tokens to every session and 888 once invoked, about $0.0004 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
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.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.