incident-response-plan-drafting SKILL.md skillA
incident-response-plan-drafting from better-isms/grcskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add better-isms/grcskills/incident-response-plan-drafting@git:20261027.690016cPins git:20261027.690016c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- better-isms/grcskills
- Path
skills/tristan-roth/incident-response-plan-drafting/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261027.690016c, committed Oct 27, 2026
- First version recorded
- Oct 19, 2026
- Size
- 8,811 bytes
- Repository stars
- 56
- License
- MIT
Use this skill when a company has no incident response plan, has one copied from a template that names teams it does not have, or an auditor, customer or insurer asks for it, and the team says "write our incident response plan", "IR plan", "security incident procedure", "who does what in an incident", "incident playbooks", "contact tree for incidents" or "our plan failed in the last incident". Drafts a plan sized to the company with roles and deputies, a severity scale, a contact tree with an…
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
Use this to write or rewrite the plan, not during a live incident (use the triage skill then). You get a new folder, `./incident-response-plan-drafting/`, holding: the plan, under ten pages, for the owner to approve (`incident-response-plan.md`); a one-page cheat sheet for 3am (`quick-reference.md`); who to call, by role, with blanks for names and numbers (`contact-tree.md`); and a one-page guide per likely incident, such as ransomware or a lost laptop (`playbooks/`). This skill drafts for a human to review and sign; this skill never marks a control effective. End `incident-response-plan.md` with `## Not checked`: what this run did not read or could not open, what it assumed and what it did not verify, specific to this run. Then add a blank `## Review record` for the approver: reviewer role and competence basis, items sampled and the source each was traced to, what was changed or rejected, one item the draft did not flag and what checking it showed, decision, date and draft version reviewed. ## Inputs to gather …
Read the whole file at its exact version.
How to install
mdr add better-isms/grcskills/incident-response-plan-drafting@sha256:a7bfdbd2afcbbf56The line at the top of this page pins the label git:20261027.690016c, 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_bs4yr3y3mbhndbsv)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 19, 2026 and Oct 27, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.690016c latest | 2026-10-27 | 690016c | 8,811 B | A | view · diff |
| git:20261027.94f7f3e | 2026-10-27 | 94f7f3e | 8,685 B | A | view · diff |
| git:20261019.20937b5 | 2026-10-19 | 20937b5 | 8,104 B | A | view · diff |
| git:20261019.3c6cd53 | 2026-10-19 | 3c6cd53 | 7,944 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 (8811 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
better-isms/grcskills · 56 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bs4yr3y3mbhndbsv GET https://markdownregistry.com/api/v1/resolve?ref=better-isms/grcskills/incident-response-plan-drafting GET https://markdownregistry.com/api/v1/blob/a7bfdbd2afcbbf566d8d4cd73835b49230d786ccb4c327447b760b6cf6675b9b
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.