exploits

Identify and summarize exploit intelligence for repository dependencies.

9|1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Vulnetix/pix-ai-coding-assistant --skill exploits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exploits
Source: https://github.com/Vulnetix/pix-ai-coding-assistant/tree/main/vulnetix/skills/exploits
Command: npx skills add https://github.com/Vulnetix/pix-ai-coding-assistant --skill exploits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes and consolidates exploit intelligence to inform vulnerability analysis and remediation planning for repositories and their dependencies.

Core Features & Use Cases

  • Collects CVE/EPSS/KEV data, PoC references, advisories, and potential attack vectors for the repository.
  • Generates threat model context with MITRE ATT&CK mappings and CWSS scoring to guide remediation planning.
  • Maintains a central vulnerability memory entry to track decisions, history, and fixes across sessions.
  • Use Case: A security engineer analyzes a new vulnerability in a transitive dependency and prepares a remediation plan with upgrade paths and mitigations.

Quick Start

Run the exploit analysis workflow on a selected vuln id to fetch data, assess impact, and update the vulnerability memory.

Frequently Asked Questions about exploits

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze exploit intelligence for vulnerabilities in transitive dependencies?

You analyze exploit intelligence by collecting CVEs, GHSA IDs, EPSS, and CISA KEV data across direct and transitive dependencies, then generating a threat report with CWSS scoring and MITRE ATT&CK mappings to guide remediation.

What is CWSS scoring and how does it help with vulnerability remediation planning?

CWSS scoring quantifies vulnerability severity and risk context to guide remediation planning. It evaluates exploit intelligence and threat model data to help prioritize fixes across your repository dependencies.

Can I track vulnerability analysis history and remediation decisions across sessions?

Yes, you can track vulnerability analysis history across sessions. The workflow maintains a central vulnerability memory entry to record decisions, history, and fixes for tracking findings over time.

Does this vulnerability analysis workflow support CISA KEV and EPSS data?

Yes, the vulnerability analysis workflow supports CISA KEV and EPSS data. It collects these metrics alongside CVEs, GHSA IDs, PoC references, and advisories to consolidate exploit intelligence for your repository.

How do I generate a threat report from CVEs and proof of concept references?

You generate a threat report by running the exploit analysis workflow on a selected vulnerability ID. It fetches CVEs, PoC references, advisories, and potential attack vectors, then produces a concise report with MITRE ATT&CK mappings.

What is the best way to prepare a remediation plan for a new exploit in a dependency?

The best way to prepare a remediation plan is to assess the exploit's impact using threat model data and CWSS scoring, identify mitigations and upgrade paths, and update the vulnerability memory entry to track the remediation decisions.