agentsclimarketplace
Sign in

Security vulnerability management

Skill planifest/planifest-framework/planifest-framework/external-skills/security-vulnerability-management

Security workflow for vulnerability intake, triage, remediation planning, and fix verification. Use when vulnerabilities from scans, reports, or incidents must be prioritized and driven to closure; do not use for incident command during ongoing active compromise.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill security-vulnerability-management

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, 419 tokens by cl100k_base, as published. Nobody here has run it

Security Vulnerability Management

Overview

Use this skill to run vulnerability handling as an evidence-based lifecycle instead of ad hoc ticket triage.

Scope Boundaries

  • Vulnerabilities arrive from SAST/DAST/dependency scans, bug bounty, or manual review.
  • Teams need severity ranking, SLA targets, and remediation sequencing.
  • Fix validation and closure criteria must be standardized.

Templates And Assets

  • Vulnerability triage template:
    • assets/vulnerability-triage-template.csv

Inputs To Gather

  • Vulnerability source, technical details, and reproduction evidence.
  • Asset criticality, exploitability context, and external exposure.
  • Available mitigations, patch options, and rollout constraints.
  • Regulatory or contractual remediation time limits.

Deliverables

  • Prioritized vulnerability backlog with severity rationale.
  • Remediation plan that includes compensating controls when full fixes are delayed.
  • Verification evidence for each fixed item.
  • Metrics for aging, SLA breach risk, and recurrence patterns.

Workflow

  1. Normalize intake records and remove duplicates while preserving traceability in assets/vulnerability-triage-template.csv.
  2. Classify severity using impact, exploitability, and environment exposure.
  3. Decide remediation path: patch, configuration hardening, feature disablement, or compensating control.
  4. Assign owner and due date by severity/SLA with explicit escalation path.
  5. Validate fixes in code and runtime behavior, including regression checks.
  6. Close only after evidence confirms exploit path is removed or acceptably mitigated.
  7. Feed recurring classes back into secure coding and architecture guardrails.

Quality Standard

  • Severity and priority decisions are explainable and consistent.
  • High-risk items have rapid mitigation even before permanent fixes.
  • Closure requires objective verification evidence.
  • Program metrics expose backlog health and systemic weaknesses.

Failure Conditions

  • Stop when critical vulnerabilities have no assigned owner or mitigation path.
  • Stop when issues are closed without fix verification evidence.
  • Escalate when SLA breach risk is imminent for high-severity items.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,835. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.