incident-response SKILL.md skillA
incident-response from cbrock84/headcount is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cbrock84/headcount/incident-response@git:20260916.0e7cd01Pins git:20260916.0e7cd01 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cbrock84/headcount
- Path
plugins/security/skills/incident-response/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260916.0e7cd01, committed Sep 16, 2026
- First version recorded
- Aug 29, 2026
- Size
- 4,096 bytes
- Repository stars
- 2,543
- License
- MIT
Runs a security incident from detection to closure — triage, containment, investigation, communication, and the review afterward. Use this when a compromise is suspected or confirmed, when preparing an incident response plan or running an exercise, when deciding whether something is an incident, or when a breach may trigger notification obligations.
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 response > Breach notification runs on statutory clocks, measured in hours in several regimes. Involve Legal > & Risk and qualified counsel as soon as personal data may be involved — not after the technical > work is done. ## Decide it is an incident, and say so The most expensive delay is the hour spent debating whether this is really an incident. Declare early; standing down a declared incident is cheap, and discovering an hour late that it was real is not. Name an **incident commander** immediately. One person, coordinating, not doing the technical work. Everyone else has a defined job. Incidents fail on coordination far more than on technical capability. ## Order of operations **1. Contain before investigating.** Stop the bleeding: isolate the host, revoke the credential, disable the account, block the path. It is tempting to watch the attacker to learn more — do that only with a deliberate decision, not by default. **2. Preserve evidence while containing.** Snapshot before you rebuild. Capture volatile state — memory, connections, running processes — before powering anything off. Rebuilding a compromised host …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/incident-response@sha256:618efd67adade17dThe line at the top of this page pins the label git:20260916.0e7cd01, 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_4bl4txtiupndnfgb)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 29, 2026 and Sep 16, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.0e7cd01 latest | 2026-09-16 | 0e7cd01 | 4,096 B | A | view · diff |
| git:20260901.a52f5a7 | 2026-09-01 | a52f5a7 | 3,757 B | A | view · diff |
| git:20260901.aa45383 | 2026-09-01 | aa45383 | 3,757 B | A | view · diff |
| git:20260829.4c1a9d2 | 2026-08-29 | 4c1a9d2 | 3,418 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 (4096 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
cbrock84/headcount · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4bl4txtiupndnfgb GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/incident-response GET https://markdownregistry.com/api/v1/blob/618efd67adade17d444b68da643009e7ec6dc23128e30ac9d4b63290e4b0bb59
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 cbrock84/headcount
Every file in cbrock84/headcount