Vuln Tracker

Categorize vuln-scanner outputs with GitHub PR state and security advisories.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/swarm-ai-research/aeon --skill vuln-tracker-swarm-ai-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Vuln Tracker
Source: https://github.com/swarm-ai-research/aeon/tree/main/skills/vuln-tracker
Command: npx skills add https://github.com/swarm-ai-research/aeon --skill vuln-tracker-swarm-ai-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Vuln Tracker automates the daily audit of vuln-scanner outputs, merges with GitHub PRs, and surfaces maintainer responses needing replies to prevent disclosure drift.

Core Features & Use Cases

  • Load and reconcile vuln-scanner scans from memory with live GitHub PR state and security advisories.
  • Categorize entries by status (merged, open-clean, needs-answer, stale-no-review, aging-engaged, queued, newly-actionable, lost-draft, pre-history).
  • Update a living dashboard in memory/vuln-followup.md and notify operators of actionable items.

Quick Start

Run the vuln-tracker skill to audit vuln-scanner outputs and surface items requiring operator action from memory/vuln-scanned.json.

Frequently Asked Questions about Vuln Tracker

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

FAQPage Schema
How do I track vulnerability disclosures across GitHub PRs and memory history?

Daily vulnerability tracking works by loading vuln-scanner scans from memory and reconciling them with live GitHub PR states and security advisories. It categorizes entries by status to surface maintainer responses needing replies, preventing disclosure drift through a living dashboard.

How do I automate daily security PR audits to prevent disclosure drift?

Automate daily security PR audits by running the tracker against memory/vuln-scanned.json to merge scanner outputs with GitHub PRs. It categorizes items by status—merged, open-clean, needs-answer, stale-no-review, aging-engaged—and updates a living dashboard in memory/vuln-followup.md to notify operators of actionable items.

What is the best way to generate a daily operator dashboard for vulnerability scanner outputs?

Generate a daily operator dashboard by applying the tracker across memory history, GitHub PR state, and security advisories. It categorizes vuln-scanner outputs into actionable statuses and writes the results to memory/vuln-followup.md, ensuring operators are notified of items requiring immediate replies or review.

Can I categorize stale security PRs and missing memory entries from vuln-scanner results?

Categorize stale security PRs and missing memory entries using safe defaults built into the tracker. It robustly handles missing memory, skipped items, pre-history PRs, and archive states, sorting them into categories like stale-no-review, lost-draft, and pre-history to ensure no vulnerability disclosure is overlooked.

How does vuln tracking handle pre-history PRs and archive states safely?

Vuln tracking handles pre-history PRs and archive states safely by applying safe defaults during the reconciliation process. It ensures robust handling of missing memory and skipped items, categorizing them appropriately as pre-history or archived so that historical vulnerability disclosures remain tracked without breaking the daily dashboard generation.