vulnerability-management SKILL.md skillA
vulnerability-management 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/vulnerability-management@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/vulnerability-management/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260916.0e7cd01, committed Sep 16, 2026
- First version recorded
- Aug 29, 2026
- Size
- 4,299 bytes
- Repository stars
- 2,543
- License
- MIT
Runs the loop from discovering a weakness to confirming it is fixed — scanning, triage, prioritization by real exploitability, remediation tracking, and patch policy. Use this to stand up or fix a vulnerability program, triage scanner output, decide what to fix first, set patch SLAs, handle a disclosure from an outside researcher, or report posture to leadership.
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
# Vulnerability management Scanners are cheap and produce more findings than any team can fix. The whole discipline is deciding what actually matters and closing those. ## Prioritize by exploitability, not by score A published severity score describes the vulnerability in the abstract. What matters is your instance of it. Rank by: - **Is it reachable?** Internet-facing beats internal beats unreachable code path by a wide margin. A critical in a dependency you import but never call is not a critical for you. - **Is it being exploited in the wild?** Known-exploited status should outrank a higher score that nobody is using. - **What does exploitation yield here?** Compromise of the system holding customer data outranks the same bug on a build agent. - **Is there a compensating control**, and does it actually work? A queue sorted purely by severity guarantees the team spends its time on the wrong things while a medium-rated, internet-facing, actively exploited bug waits. ## Triage discipline Every finding gets one of four outcomes, each recorded: **fix**, **mitigate**, **accept** (with an expiry and a named owner), or **false positive** (with the reason). …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/vulnerability-management@sha256:505d5042a987b67bThe 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_dnou7eirj25xxxmy)
3 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,299 B | A | view · diff |
| git:20260901.0757404 | 2026-09-01 | 0757404 | 3,960 B | A | view · diff |
| git:20260901.aa45383 | 2026-09-01 | aa45383 | 3,585 B | A | view · diff |
| git:20260829.4c1a9d2 | 2026-08-29 | 4c1a9d2 | 3,248 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 (4299 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_dnou7eirj25xxxmy GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/vulnerability-management GET https://markdownregistry.com/api/v1/blob/505d5042a987b67b7cdd992062e9597b610e57457066b6f9c9257ffc7b3bb6a2
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