vulnerability-management skillA
vulnerability-management is agent-read markdown (skill) from miosa-osa/osa: Prioritize vulnerabilities using exact affected versions, reachable exposure and known exploitation, then patch and retest with rollback. Use for vulnerability management, patch prioritization, KEV matching, dependency risk or verifying a security fix..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Vulnerability Management ## Workflow 1. Collect resolved software versions, asset owners and exposure evidence; distinguish product names from exact package identities. 2. Compare vendor advisories and a dated CISA KEV export; read the local JSON matching example. KEV absence never proves safety. 3. Confirm affected version ranges and reachable attack conditions; rank exploitation evidence, exposure and business impact together. 4. Prepare vendor-supported remediation, compatibility checks and a tested rollback path. 5. Verify installed and running versions after remediation, then rerun the original security check plus normal functional controls. 6. Record remaining exceptions, compensating controls, owner and revisit date; do not call a version bump alone a verified fix. ## Worked example and prerequisites Read [references/workflow.md](references/workflow.md) before execution. Use only registered OSA tools named in the frontmatter; command examples run through `shell_execute`. Check `command -v` for each external executable on the actual target. Optional packages, external collectors and vendor accounts are not bundled or presumed installed. ## Evidence and completion …
Read the whole file at its exact version.
How to install
mdr add miosa-osa/osa/vulnerability-management@v1.0.200mdr add miosa-osa/osa/vulnerability-management@sha256:c7f27f4c4cca885fPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_u3bk662ino2cizuj)
1 badge views in 30 days
Versions
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 (2292 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
miosa-osa/osa · 74 stars · license NOASSERTION · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_u3bk662ino2cizuj GET https://markdownregistry.com/api/v1/resolve?ref=miosa-osa/osa/vulnerability-management GET https://markdownregistry.com/api/v1/blob/c7f27f4c4cca885f41b96e425707e2f633935201045190863f6c3dcaf759b7cd
Your agent 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.