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/intimatep/pentestclaw/cve-intelnpx skills add intimatep/PenTestClaw --skill cve-intelgit clone --depth 1 https://github.com/intimatep/PenTestClawWrote 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/intimatep/pentestclaw/cve-intel)<a href="https://agentmods.dev/skills/intimatep/pentestclaw/cve-intel"><img src="https://agentmods.dev/badge/skills/intimatep/pentestclaw/cve-intel.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 | $0.00038 | $0.00653 |
| Opus 5 | $0.00019 | $0.00327 |
| Sonnet 5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
cve_intel 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 5d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 5d ago First seen · 66 lines · 38 tokens per session scan A 0a42b5beeec9
cve_intel is a skill published in the GitHub repository intimatep/PenTestClaw (11 stars, last pushed 5mo ago), with no licence file. It adds 38 tokens to every session and 653 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
vulnerability-db
A practical guide for AI agents that need to use vdb. If you are changing the code rather than using it, read AGENTS.md instead.
analyzing-sbom-for-supply-chain-vulnerabilities
Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports.…
fix-plan
Generate an EPSS/KEV-prioritised remediation plan from a scan. Returns the top findings ranked by real-world exploitation risk with copy-paste upgrade commands, semver-jump risk classification (PATCH/MINOR/MAJOR), and a recommendation per package. Use when the user asks for "what should I fix first", "remediation…
scan-full
Comprehensive scan covering project dependencies PLUS OS/system packages (Homebrew on macOS, apt/dnf on Linux) PLUS installed IDE extensions (VS Code marketplace + JetBrains plugins). Most other supply-chain scanners only check project manifests and miss system + IDE surfaces. Use whenever the user asks for "complete…
supply-chain-scan
Scan a workspace for supply-chain CVEs across project dependencies, system packages (Homebrew/apt), and IDE extensions (VS Code, JetBrains). Findings ranked by EPSS exploit probability and CISA KEV presence — not just CVSS severity. Use when the user asks about supply-chain risk, dependency vulnerabilities, or wants…
why
Explain why a specific vulnerable package is in the project — direct vs transitive dependency, which CVE IDs apply, EPSS exploit-probability score, whether it's on the CISA KEV catalog, and the recommended fix command. Use when the user asks "why is X vulnerable", "where does X come from", or "is X actually…