Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/jayrha/agentskills/vulnerability-triagenpx skills add JayRHa/AgentSkills --skill vulnerability-triagegit clone --depth 1 https://github.com/JayRHa/AgentSkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jayrha/agentskills/vulnerability-triage)<a href="https://agentmods.dev/skills/jayrha/agentskills/vulnerability-triage"><img src="https://agentmods.dev/badge/skills/jayrha/agentskills/vulnerability-triage.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00154 | $0.02429 |
| Opus 5 | $0.00077 | $0.01215 |
| Sonnet 5 | $0.00031 | $0.00486 |
| Haiku 4.5 | $0.00015 | $0.00243 |
Grade A, and why
vulnerability-triage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability Triage
Overview
Vulnerability triage turns a flood of scanner findings or a single CVE into a ranked, justified, time-bound remediation decision. CVSS alone is a poor prioritizer: only a small fraction of CVEs are ever exploited, and a "Critical" CVSS on an isolated internal box may matter far less than a "Medium" on an internet-facing crown-jewel system.
This skill scores each vulnerability across four dimensions and combines them:
- Severity — CVSS base + temporal (intrinsic technical impact).
- Exploitability — EPSS probability, CISA KEV listing, public exploit/PoC, weaponization.
- Exposure — attack vector, internet-facing, network reachability, authentication/preconditions, compensating controls.
- Business impact — asset criticality, data sensitivity, blast radius, regulatory scope.
Keywords: CVE, CVSS, EPSS, CISA KEV, exploitability, attack vector, remediation SLA, patch priority, vulnerability management, risk score, false positive, compensating control, SSVC, internet-facing, privilege escalation.
When to Use
- Triaging output from Nessus / Qualys / Tenable / Trivy / Grype / Dependabot / Snyk.
- Deciding patch urgency for a newly disclosed CVE.
- Writing a vulnerability risk assessment or exception/risk-acceptance memo.
- Deduplicating and clustering scanner findings by root cause.
- Justifying why something is (or is not) urgent to leadership or auditors.
Workflow
Follow these steps in order. For a single CVE, steps 2-5 take minutes; for a
scan, batch through scripts/triage.py first, then hand-review the top tier.
1. Normalize and deduplicate the input
- Collapse duplicate findings: same CVE + same package/component on the same host is one finding instance; many hosts = one vuln with N instances.
- Group by root cause (e.g., one vulnerable
opensslversion → all dependent findings). Patching the root usually clears the cluster. - Drop confirmed false positives (see references/false-positives.md) before scoring.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 172 lines · 154 tokens per session scan A 482b4e6bee17
vulnerability-triage is a skill published in the GitHub repository JayRHa/AgentSkills (4 stars, last pushed 1mo ago), licensed MIT. It adds 154 tokens to every session and 2,429 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
cost-optimizer
Trigger when the user asks to audit Claude Code costs, reduce token spend, says "my Claude bill is too high", "optimize my CLAUDE.md", "why is this project burning tokens", or "/cost-optimizer". Scans a project for the common Claude Code cost leaks and returns a prioritized fix list.
excalidraw-architecture
Trigger when the user asks for an architecture diagram, says "draw the system", "update the architecture diagram", "give me an excalidraw of this codebase", or "/excalidraw-architecture". Generates or updates an Excalidraw JSON file at docs/architecture.excalidraw by reading the codebase's key entry points.
model-cost-compare
Trigger when the user asks which model to use, wants to compare model costs, says "what's cheapest for this task", "should I use Opus or Sonnet", "can a smaller model handle this", or "/model-cost-compare". Estimates token cost across Opus 4.6, Sonnet 4.6, GLM-5.1, Minimax M2.7, and local Gemma 4, then recommends the…
openclaw-debugger
Trigger when an OpenClaw agent is broken, silent, crashing, stuck, not responding, returning empty output, or the user says "my agent is down", "agent not working", "/openclaw-debugger". Walks through the standard OpenClaw 2026.4 diagnosis checklist and prints a report.
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.
meeting-notes
Paste raw meeting notes and get a clean summary with key decisions and action items.