incident-commander SKILL.md skillA
incident-commander from event4u-app/agent-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add event4u-app/agent-config/incident-commander@git:20260823.b258448Pins git:20260823.b258448 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- event4u-app/agent-config
- Path
src/skills/incident-commander/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260823.b258448, committed Aug 23, 2026
- First version recorded
- Jun 3, 2026
- Size
- 5,532 bytes
- Repository stars
- 18
- License
- MIT
Use during or right after an incident — frames severity, sets comms cadence, drafts the post-mortem skeleton — even when the user just says 'production is down' or 'wir haben einen Vorfall'.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# incident-commander > Run the **coordination layer** during an incident: classify > severity, set comms cadence, hold a clean timeline, and draft the > post-mortem skeleton when the dust settles. This skill does **not** > debug the system — that is the engineer's job. The commander keeps > the room oriented so the engineer can think. ## When to use - Production is degraded or down and someone needs to coordinate. - A critical job, queue, or third-party is failing and the team is scrambling. - A near-miss happened and a post-mortem is being drafted. - German triggers: "Vorfall", "Prod ist down", "wer übernimmt Comms?". Do NOT use when: - The system is healthy and the concern is a future outage — route to [`risk-officer`](../risk-officer/SKILL.md) instead. - The user wants the bug fixed — route to `/bug-investigate` and `/bug-fix`. The commander coordinates; engineers debug. - The incident is a security breach — route to [`threat-modeling`](../threat-modeling/SKILL.md) first; the commander still runs comms but the response shape changes. ## Procedure ### 1. Inspect the signal and classify severity | SEV | Trigger | |---|---| …
Read the whole file at its exact version.
How to install
mdr add event4u-app/agent-config/incident-commander@sha256:8a5ba02dd2146887The line at the top of this page pins the label git:20260823.b258448, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6odqq2ufjiohxdfj)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 3, 2026 and Aug 23, 2026, about one every 81 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260823.b258448 latest | 2026-08-23 | b258448 | 5,532 B | A | view · diff |
| git:20260603.668ed88 | 2026-06-03 | 668ed88 | 5,035 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5532 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
event4u-app/agent-config · 18 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6odqq2ufjiohxdfj GET https://markdownregistry.com/api/v1/resolve?ref=event4u-app/agent-config/incident-commander GET https://markdownregistry.com/api/v1/blob/8a5ba02dd21468871e0605dc1b0a37ee285cb1a2db00f717837ecde1e19edad0
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from event4u-app/agent-config
Every file in event4u-app/agent-config