incident-to-remediation-protocol SKILL.md skillA
incident-to-remediation-protocol from vincentchuwaichow/vanguard-frontier-agentic is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vincentchuwaichow/vanguard-frontier-agentic/incident-to-remediation-protocol@v0.1.0Pins v0.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vincentchuwaichow/vanguard-frontier-agentic
- Path
skills/cross-functional/incident-to-remediation-protocol/SKILL.md- Versions recorded
- 2
- Latest version
- v0.1.0, committed Jul 31, 2026
- First version recorded
- Jun 17, 2026
- Size
- 9,045 bytes
- Repository stars
- 24
- License
- Apache-2.0
Use this skill when a security incident must be triaged, contained, remediated, and reviewed in a Zero Trust assume-breach posture across Microsoft 365 and Dynamics 365 environments. Defines the end-to-end flow from detection through severity triage, containment approval, investigation, remediation, and post-incident review. Applies Zero Trust principles — verify explicitly, use least privilege, assume breach — throughout. Does not serve as an authorization to isolate devices, block users, or…
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-to-Remediation Protocol ## Purpose This skill defines how a security incident detected across Microsoft 365 or Dynamics 365 is triaged, classified by severity, contained, investigated, remediated, and reviewed in a Zero Trust posture. It applies the assume-breach principle throughout: the scope of compromise is always assumed to be larger than initial signals suggest until evidence proves otherwise. It does not authorize containment or remediation actions; those require the incident commander or security owner. It does not replace a qualified SecOps team or Microsoft Defender XDR escalation. ## When to use - A security incident has been detected in the Microsoft Defender portal (Microsoft Defender XDR) or reported through another channel. - An identity compromise, device compromise, data exfiltration signal, or malicious configuration change is suspected in Microsoft 365 or Dynamics 365. - A SecOps team needs a structured workflow for triage, containment approval, investigation, and post-incident review. …
Read the whole file at its exact version.
How to install
mdr add vincentchuwaichow/vanguard-frontier-agentic/incident-to-remediation-protocol@sha256:ebfdfcedfa9751eaThe line at the top of this page pins the label v0.1.0, 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_etivbal6qmlyltdp)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 17, 2026 and Jul 31, 2026, about one every 44 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.1.0 latest | 2026-07-31 | e5f8521 | 9,045 B | A | view · diff |
| v0.1.0 | 2026-06-17 | 50d7ede | 9,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 (9045 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
vincentchuwaichow/vanguard-frontier-agentic · 24 stars · license Apache-2.0 · pushed 2026-10-20 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_etivbal6qmlyltdp GET https://markdownregistry.com/api/v1/resolve?ref=vincentchuwaichow/vanguard-frontier-agentic/incident-to-remediation-protocol GET https://markdownregistry.com/api/v1/blob/ebfdfcedfa9751ea8b03c3dabe29e3bd4bf9ed6ebc27f800b3c0290b82051357
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.