cyber-audit
Run read-only exposure checks for security advisories and write a structured local audit report.
Profile →npx skills add sickn33/agentic-awesome-skills --skill cyber-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# cyber-audit ## When to Use - Use when the user asks whether their machine or projects are affected by a CVE, breach, or package advisory. - Use when a read-only local security exposure report is appropriate. ## Hard rules - **Read-only.** No installs, removes, upgrades, restarts, network calls, or file modifications outside `~/Documents/security-audits/`. - **No `sudo`.** Never. - **One report per invocation.** Always end by writing the `.md` file (even if the verdict is "Not affected" — the audit trail matters). - If a check requires a state-changing command, **skip it and note "not checked (would require state change)"** in the table. Do not run it. ## Workflow 1. **Identify scope.** Extract from the advisory: package/binary name, affected versions, platform (macOS / Linux / Windows), attack vector (supply chain / RCE / local / network). 2. **Run checks in parallel** (Bash tool, multiple calls in one message). Pick relevant checks for the advisory type — don't run all of them. 3. **Build the table** as you go. Each row = one check + concrete result (version number, path, "None", "N/A"). 4. **Write the report** to `~/Documents/security-audits/YYYY-MM-DD-<short-kebab-slug>.md`. U
- When to Use
- Hard rules
- Workflow
- Check menu (pick what's relevant)
- Report template
- Verdict wording
- When to break the read-only rule
- Reference
- Limitations
which npm pnpm yarn; npm root -g; pnpm root -g 2>/dev/null ls /opt/homebrew/lib/node_modules # global npm find ~ -maxdepth 8 -type d -name "<pkg>" 2>/dev/null \ find ~/Documents ~/Desktop ~/Downloads -maxdepth 8 -type f \ which python3 pip pipx uv pip list 2>/dev/null | grep -i "<pkg>" find ~/Documents -maxdepth 6 -name "requirements*.txt" -o -name "pyproject.toml" \ brew list --versions <formula> 2>/dev/null which <binary>; <binary> --version 2>/dev/null pgrep -lf "<binary>"
What does the cyber-audit skill do?
Run read-only exposure checks for security advisories and write a structured local audit report.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill cyber-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.