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 skills add Unclecheng-li/DeepSec --skill cve-triagegit clone --depth 1 https://github.com/Unclecheng-li/DeepSecWrote 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/unclecheng-li/deepsec/cve-triage)<a href="https://agentmods.dev/skills/unclecheng-li/deepsec/cve-triage"><img src="https://agentmods.dev/badge/skills/unclecheng-li/deepsec/cve-triage/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/unclecheng-li/deepsec/cve-triage"><img src="https://agentmods.dev/badge/skills/unclecheng-li/deepsec/cve-triage.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.00616 |
| Opus 5 | $0.00022 | $0.00308 |
| Sonnet 5 | $0.00009 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
cve-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 9d 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.
This is a copy
100% identical to cve-triage — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CVE Triage
Turn version/banner evidence from recon into a prioritized, exploitability-aware
list of CVEs worth verifying. Use this after fingerprinting a service, when a
banner or Server: header reveals a product and version, or whenever the target
exposes software with a known version.
The cve_lookup tool
VulnClaw ships a read-only cve_lookup tool backed by NVD:
- Keyword search —
cve_lookup(query="Apache httpd 2.4.49", limit=5)returns the top CVEs sorted by CVSS, highest first. - CVE-ID detail —
cve_lookup(query="CVE-2021-44228")returns the full record plus best-effort exploit / PoC repositories discovered on GitHub.
It performs no egress to the target and is safe during recon. Without an
NVD_API_KEY it still works (lower rate limit); set one for heavier use.
Workflow
- Extract product + version from recon — service banners,
Serverheaders, JS bundles, login footers, package manifests. A precise version string (OpenSSH 8.2p1,nginx 1.18.0) yields far better matches than a bare name. - Query
cve_lookupwith"<product> <version>". Pull the detail record for any high/critical hit by re-querying itsCVE-ID. - Score & prioritize — see
references/cve-triage-workflow.md. Rank by CVSS, then by exploit availability, then by exposure (is the vulnerable surface actually reachable on this target?). - Confirm version applicability — match the target's version against the
CVE's affected
cperange before claiming it. Banner ≠ proof of vulnerability. - Record findings with the CVE-ID, CVSS, and the evidence that maps this target to it. Mark unconfirmed version-only matches as needs-manual-review, not verified.
Pitfalls
- A keyword match is a hypothesis, not a finding — version ranges and backported patches mean a banner version can be patched in place.
- GitHub "PoC" repos are unverified third-party code; treat as leads, never run blindly against a target.
- Prefer the CVSS base score for triage, but let exploit availability and real exposure override raw score when prioritizing verification effort.
What ships with it
1 file 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.
- 9d ago First seen · 52 lines · 44 tokens per session scan A 9cf49c8ef992
cve-triage is a skill published in the GitHub repository Unclecheng-li/DeepSec (402 stars, last pushed 15d ago), licensed MIT. It adds 44 tokens to every session and 616 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cve-triage, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
final-report
Final engagement report generation — executive summary, technical report, findings aggregation, attack path narrative, detection gap matrix, remediation roadmap.
exploit-reporting
Exploitation finding documentation — initial access reports, exploit chain documentation, CVSS v4.0 scoring, shell/credential inventory, detection gap analysis.
ti-ioc-extraction
Automated IOC extraction from threat reports, logs, and unstructured text — parse hashes, IPs, domains, URLs, email addresses, and CVEs. Covers regex-based extraction, defanging/refanging, bulk hash lookup, IOC deduplication, YARA rule generation from IOCs, and STIX/TAXII formatting for sharing.
m365-mailbox-compromise
Microsoft 365 mailbox compromise chain — OAuth consent phishing, delegate access abuse, mail rule persistence, and token theft via device code phishing. Full kill chain from initial access to persistent email collection.
web
Web application exploitation — the primary category skill for all web-based attacks. This is a routing skill: read this first to identify the attack type, then load the appropriate specialized sub-skill for detailed procedures. Covers 11 technique areas across injection, file access, authentication, and API…
opsec
Operational security management — traffic shaping, scan rate limiting, source IP management, tool signature avoidance, evidence handling, anti-detection patterns.