cyber-audit

Audits local machine exposure to CVEs and supply-chain advisories with read-only checks.

60|11|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/matyasstoch/david-skills --skill cyber-audit-matyasstoch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cyber-audit
Source: https://github.com/matyasstoch/david-skills/tree/main/skills/cyber-audit
Command: npx skills add https://github.com/matyasstoch/david-skills --skill cyber-audit-matyasstoch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a new CVE, breach, or malicious package advisory drops, you need to know quickly whether your machine and projects are affected without risking further damage. This Skill performs a strictly read-only exposure audit and produces a structured, dated report. ## Core Features & Use Cases - Read-only system checks: Runs parallel Bash checks across npm/pnpm/yarn, Python, Homebrew, running processes, listeners, LaunchAgents, environment variables, and VS Code extensions — never installing, removing, or modifying anything. - Structured audit reports: Writes a terse, factual Markdown report to ~/Documents/cyber/YYYY-MM-DD-<slug>.md with a check table, verdict (Not affected / Affected / Partially affected), and follow-ups. - Use Case: A supply-chain advisory names a malicious npm package. Ask the agent to check if you're affected; it greps your lockfiles and global modules, inspects running processes, and writes a dated report with a clear verdict and remediation commands for you to run yourself. ## Quick Start Ask the agent to audit your machine for a specific advisory, for example: "Check if I'm affected by the malicious version of package X and write a report."

Frequently Asked Questions about cyber-audit

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

FAQPage Schema
How do I check if my machine is affected by a CVE or malicious npm package?▼

Share the advisory details and ask for an audit. The Skill greps package.json and lockfiles across your projects, checks global npm/pnpm modules, and inspects running processes, then writes a dated report with a clear affected or not-affected verdict.

How to audit my system for a supply-chain attack without changing anything?▼

This Skill is strictly read-only: it never installs, removes, upgrades, or modifies files outside the audit report folder. Checks that would require state changes are skipped and noted as not checked in the report table.

Does the audit cover Python and Homebrew packages too?▼

Yes. Beyond npm/pnpm/yarn, it checks pip lists, requirements.txt, pyproject.toml, poetry.lock, uv.lock, Homebrew formulas, system binaries, running processes, network listeners, LaunchAgents, and VS Code extensions.

What happens if the audit finds I'm affected by a vulnerability?▼

The report verdict states Affected or Partially affected with rationale bullets, and the remediation command is listed under Follow-ups. The Skill never runs the fix itself — you execute it manually.

Where are the audit reports saved?▼

Reports are written as Markdown files to ~/Documents/cyber/ named with the date and a short slug, such as 2026-05-10-ollama-bleeding-llama.md, matching the terse style of existing reports in that folder.