New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Prioritizing Vulnerabilities With Cvss Scoring

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

The Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity.

Apache-2.0Auto-check passedDevOps & Cloud

Install Prioritizing Vulnerabilities With Cvss Scoring

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill prioritizing-vulnerabilities-with-cvss-scoring -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills prioritizing-vulnerabilities-with-cvss-scoring --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/prioritizing-vulnerabilities-with-cvss-scoring .claude/skills/prioritizing-vulnerabilities-with-cvss-scoring && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prioritizing-vulnerabilities-with-cvss-scoring
GitHub stars
34k
Token cost
~1.9k tokens
SKILL.md length
675 words
Files
8 (incl. scripts, references, assets)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0

At a glance

The Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity.

  • Works in 4 steps: Base Metrics (Intrinsic Severity) → Threat Metrics (Dynamic Context) → Environmental Metrics… → …
  • Tasks that involve Incident response
  • SKILL.md covers Overview, When to Use, Prerequisites and Core Concepts, plus 4 more sections
  • Runs Python scripts from its folder

What it does

Prioritizing Vulnerabilities With Cvss Scoring is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. The Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity. CVSS v4.0 (r

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/api-reference.md` and `references/standards.md`).

It sits in DevOps & Cloud, covering Incident response. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Incident response

Example prompts

  • “/prioritizing-vulnerabilities-with-cvss-scoring”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Base Metrics (Intrinsic Severity)
  2. Threat Metrics (Dynamic Context)
  3. Environmental Metrics (Organization-Specific)
  4. Supplemental Metrics (Advisory Information)

What it can do on your machine

Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prioritizing Vulnerabilities With Cvss Scoring loads about 1.9k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 675 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 675 words, ~1,888 tokens.

Download SKILL.mdSave it as .claude/skills/prioritizing-vulnerabilities-with-cvss-scoring/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
prioritizing-vulnerabilities-with-cvss-scoring
description
The Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity. CVSS v4.0 (r
domain
cybersecurity
subdomain
vulnerability-management
tags
vulnerability-management, cve, cvss, risk, prioritization, nist
version
1.0
author
mahipal
license
Apache-2.0
nist_csf
ID.RA-01, ID.RA-02, ID.IM-02, ID.RA-06
mitre_attack
T1190, T1203, T1068

Prioritizing Vulnerabilities with CVSS Scoring

Overview

The Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity. CVSS v4.0 (released November 2023) introduces refined metrics for more accurate scoring. This skill covers calculating CVSS scores, interpreting vector strings, and using CVSS alongside contextual factors like EPSS and CISA KEV for effective vulnerability prioritization.

When to Use

  • When managing security operations that require prioritizing vulnerabilities with cvss scoring
  • When improving security program maturity and operational processes
  • When establishing standardized procedures for security team workflows
  • When integrating threat intelligence or vulnerability data into operations

Prerequisites

  • Understanding of common vulnerability types (buffer overflow, injection, XSS, etc.)
  • Familiarity with networking concepts (attack vectors, protocols)
  • Access to NVD (National Vulnerability Database) for CVE lookups
  • Vulnerability scan results requiring prioritization

Core Concepts

CVSS v4.0 Metric Groups
1. Base Metrics (Intrinsic Severity)

Represent the inherent characteristics of a vulnerability:

Exploitability Metrics:

  • Attack Vector (AV): Network (N), Adjacent (A), Local (L), Physical (P)
  • Attack Complexity (AC): Low (L), High (H)
  • Attack Requirements (AT): None (N), Present (P) - NEW in v4.0
  • Privileges Required (PR): None (N), Low (L), High (H)
  • User Interaction (UI): None (N), Passive (P), Active (A) - Expanded in v4.0

Impact Metrics (Vulnerable System):

  • Confidentiality (VC): None (N), Low (L), High (H)
  • Integrity (VI): None (N), Low (L), High (H)
  • Availability (VA): None (N), Low (L), High (H)

Impact Metrics (Subsequent System):

  • Confidentiality (SC): None (N), Low (L), High (H)
  • Integrity (SI): None (N), Low (L), High (H)
  • Availability (SA): None (N), Low (L), High (H)
2. Threat Metrics (Dynamic Context)
  • Exploit Maturity (E): Attacked (A), POC (P), Unreported (U)
3. Environmental Metrics (Organization-Specific)

Modified versions of base metrics reflecting local deployment context, plus:

  • Confidentiality Requirement (CR): High (H), Medium (M), Low (L)
  • Integrity Requirement (IR): High (H), Medium (M), Low (L)
  • Availability Requirement (AR): High (H), Medium (M), Low (L)
4. Supplemental Metrics (Advisory Information)
  • Safety (S): Present (P), Negligible (X)
  • Automatable (AU): Yes (Y), No (N)
  • Recovery (R): Automatic (A), User (U), Irrecoverable (I)
  • Value Density (V): Diffuse (D), Concentrated (C)
  • Vulnerability Response Effort (RE): Low (L), Moderate (M), High (H)
  • Provider Urgency (U): Red, Amber, Green, Clear
CVSS v4.0 Severity Ratings
Score RangeSeverity
0.0None
0.1 - 3.9Low
4.0 - 6.9Medium
7.0 - 8.9High
9.0 - 10.0Critical
CVSS v4.0 Vector String Format
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

This example represents a network-exploitable vulnerability requiring no privileges, no user interaction, no attack requirements, with high impact on confidentiality, integrity, and availability of the vulnerable system.

Show full SKILL.md (255 more words)Show less

Workflow

Step 1: Assess Base Metrics

For each vulnerability, evaluate:

Example: CVE-2024-3094 (XZ Utils Backdoor)

Attack Vector:        Network (N)     - Exploitable over network
Attack Complexity:    High (H)        - Specific conditions required
Attack Requirements:  Present (P)     - Specific build/config needed
Privileges Required:  None (N)        - No authentication needed
User Interaction:     None (N)        - No victim action needed

Vulnerable System Impact:
  Confidentiality:    High (H)        - Complete access to SSH keys
  Integrity:          High (H)        - Arbitrary code execution
  Availability:       High (H)        - Full system compromise

Subsequent System Impact:
  Confidentiality:    High (H)        - Lateral movement possible
  Integrity:          High (H)        - Network-wide compromise
  Availability:       None (N)        - No downstream availability impact

Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N
Step 2: Apply Threat Intelligence Context

Enrich CVSS with real-world threat data:

Exploit Maturity:     Attacked (A)    - Active exploitation in the wild
EPSS Score:           0.94            - 94% probability of exploitation in 30 days
CISA KEV:            Listed           - Mandatory remediation for federal agencies
Step 3: Calculate Environmental Score

Adjust for organizational context:

Confidentiality Req:  High (H)        - Handles PII/financial data
Integrity Req:        High (H)        - Critical business process
Availability Req:     Medium (M)      - Has DR/failover capability

Modified Attack Vector: Network (N)   - Internet-facing deployment
Step 4: Multi-Factor Prioritization Matrix

Combine CVSS with additional prioritization factors:

FactorWeightSource
CVSS Base Score25%NVD/Scanner
EPSS Score25%FIRST EPSS API
Asset Criticality20%Asset inventory/CMDB
CISA KEV Listed15%CISA catalog
Network Exposure15%Network segmentation data
Step 5: Define Remediation SLAs
Priority LevelCVSS RangeEPSSAsset TierSLA
P1 - Emergency9.0-10.0>0.5Tier 124-48 hours
P2 - Critical7.0-8.9>0.3Tier 1-27 days
P3 - High7.0-8.9<0.3Tier 2-314 days
P4 - Medium4.0-6.9AnyAny30 days
P5 - Low0.1-3.9AnyAny90 days

Best Practices

  1. Never rely solely on CVSS base score for prioritization
  2. Always incorporate threat intelligence (EPSS, KEV, exploit databases)
  3. Maintain accurate asset criticality ratings in your CMDB
  4. Adjust environmental metrics for your specific deployment context
  5. Use CVSS v4.0 vector strings for precise communication between teams
  6. Document scoring rationale for audit trail and consistency
  7. Re-evaluate scores when new threat intelligence becomes available
  8. Train remediation teams on interpreting CVSS metrics and vector strings

Common Pitfalls

  • Treating CVSS base score as the sole prioritization factor
  • Ignoring environmental metrics that reflect organizational risk
  • Not updating threat metrics when exploit maturity changes
  • Confusing CVSS severity with actual organizational risk
  • Using outdated CVSS v2.0 scores instead of v3.1/v4.0
  • Over-relying on scanner-provided scores without validation
  • prioritizing-patches-with-exploit-prediction-scoring
  • implementing-risk-based-vulnerability-management
  • implementing-vulnerability-remediation-sla

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts, references, assets) in skills/prioritizing-vulnerabilities-with-cvss-scoring of mukul975/Anthropic-Cybersecurity-Skills.

  • SKILL.md
  • LICENSE
  • assets/template.md
  • references/api-reference.md
  • references/standards.md
  • references/workflows.md
  • scripts/agent.py
  • scripts/process.py

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Prioritizing Vulnerabilities With Cvss Scoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prioritizing Vulnerabilities With Cvss Scoring compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prioritizing Vulnerabilities With Cvss Scoring this skillmukul975/Anthropic-Cybersecurity-Skills34k—~1.9kAutomated safety check: PassApache-2.0
Soc Operationsbriiirussell/cybersecurity-skills413—~2.9kAutomated safety check: PassMIT
Incident Responsealirezarezvani/claude-skills28k—~3.8kAutomated safety check: PassMIT
Triaging Security Alertstrilwu/secskills157—~2.5kAutomated safety check: PassMIT
Ise Incident Responseautomateyournetwork/netclaw676—~3.4kAutomated safety check: PassApache-2.0
Responding To Incidentstrilwu/secskills157—~3.9kAutomated safety check: NotesMIT

Similar skills

  • Soc Operations

    briiirussell/cybersecurity-skills

    Build, run, and improve a Security Operations Center — alert prioritization, runbook authoring, escalation criteria, on-call structure, alert tuning workflow, MTTD / MTTR / fidelity KPIs, analyst…

    413 GitHub stars~2.9k tokensUpdated 4 mo ago
    DevOps & CloudAuto-check passed

  • Incident Response

    alirezarezvani/claude-skills

    A skill your agent uses when a security incident has been detected or declared and needs classification, triage, escalation path determination, and forensic evidence collection.

    28k GitHub stars~3.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Triaging Security Alerts

    trilwu/secskills

    Work a security alert queue to a defensible disposition — separating true positives from false positives and benign true positives, reasoning about base rates before escalating, ordering enrichment…

    157 GitHub stars~2.5k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Ise Incident Response

    automateyournetwork/netclaw

    Rapid ISE endpoint investigation and quarantine workflow - endpoint lookup, auth history, posture review, human-authorized quarantine, ServiceNow Security Incident.

    676 GitHub stars~3.4k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Responding To Incidents

    trilwu/secskills

    Run digital forensics and incident response — triage, evidence acquisition with chain of custody, host and cloud artifact analysis, timeline reconstruction, scoping, containment, eradication, and…

    157 GitHub stars~3.9k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes

  • Breach Simulation

    mukul975/Privacy-Data-Protection-Skills

    Designs and executes tabletop breach simulation exercises for testing organizational breach response capabilities.

    301 GitHub stars~2.9k tokensUpdated 6 mo ago
    DevOps & CloudAuto-check passed

More from mukul975/Anthropic-Cybersecurity-Skills

All 644 skills in this repo

  • Campaign Attribution Evidence Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Go Malware Analysis in Ghidra

    mukul975/Anthropic-Cybersecurity-Skills

    Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

  • LNK and Jump List Forensics

    mukul975/Anthropic-Cybersecurity-Skills

    Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Malware Persistence Analysis with Autoruns

    mukul975/Anthropic-Cybersecurity-Skills

    Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • NTFS MFT Deleted File Recovery

    mukul975/Anthropic-Cybersecurity-Skills

    Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Network Covert Channel Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Prioritizing Vulnerabilities With Cvss Scoring

What does Prioritizing Vulnerabilities With Cvss Scoring do?

The Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity. Prioritizing Vulnerabilities With Cvss Scoring is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. The Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity.

When should I use Prioritizing Vulnerabilities With Cvss Scoring?

Prioritizing Vulnerabilities With Cvss Scoring fits situations like: tasks that involve Incident response.

How do I install Prioritizing Vulnerabilities With Cvss Scoring in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill prioritizing-vulnerabilities-with-cvss-scoring -a claude-code`. Or copy the skill folder (skills/prioritizing-vulnerabilities-with-cvss-scoring in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/prioritizing-vulnerabilities-with-cvss-scoring in your project. Claude Code loads it when a task matches its description.

How do I install Prioritizing Vulnerabilities With Cvss Scoring in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill prioritizing-vulnerabilities-with-cvss-scoring -a codex`. Or copy the skill folder (skills/prioritizing-vulnerabilities-with-cvss-scoring in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/prioritizing-vulnerabilities-with-cvss-scoring in your project. Codex loads it when a task matches its description.

Can I use Prioritizing Vulnerabilities With Cvss Scoring in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill prioritizing-vulnerabilities-with-cvss-scoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prioritizing-vulnerabilities-with-cvss-scoring, .gemini/skills/prioritizing-vulnerabilities-with-cvss-scoring, .github/skills/prioritizing-vulnerabilities-with-cvss-scoring and .opencode/skills/prioritizing-vulnerabilities-with-cvss-scoring in your project.

What does Prioritizing Vulnerabilities With Cvss Scoring need to run?

Going by SKILL.md and its folder, Prioritizing Vulnerabilities With Cvss Scoring needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Prioritizing Vulnerabilities With Cvss Scoring access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Prioritizing Vulnerabilities With Cvss Scoring safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Prioritizing Vulnerabilities With Cvss Scoring use?

Prioritizing Vulnerabilities With Cvss Scoring is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prioritizing Vulnerabilities With Cvss Scoring use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.

What are the alternatives to Prioritizing Vulnerabilities With Cvss Scoring?

Skills that share tags, products or a category with Prioritizing Vulnerabilities With Cvss Scoring: Soc Operations (briiirussell/cybersecurity-skills, 413 stars), Incident Response (alirezarezvani/claude-skills, 28k stars), Triaging Security Alerts (trilwu/secskills, 157 stars) and Ise Incident Response (automateyournetwork/netclaw, 676 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prioritizing Vulnerabilities With Cvss Scoring?

mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.

Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.