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 JansenAnalytics/claudex --skill vuln-scannergit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/vuln-scanner)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/vuln-scanner"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/vuln-scanner.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.00046 | $0.00314 |
| Opus 5 | $0.00023 | $0.00157 |
| Sonnet 5 | $0.00009 | $0.00063 |
| Haiku 4.5 | $0.00005 | $0.00031 |
Grade A, and why
vuln-scanner 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 4d 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.
What it actually says
Vulnerability Scanner Skill
Use when: checking if any projects have security vulnerabilities, or when adding a new npm project.
Run a scan now
node ${VULN_SCANNER_HOME:-$HOME/projects/vuln-scanner}/scan.cjs
Scan specific project
node ${VULN_SCANNER_HOME:-$HOME/projects/vuln-scanner}/scan.cjs --project
Dry run (no alerts)
node ${VULN_SCANNER_HOME:-$HOME/projects/vuln-scanner}/scan.cjs --dry-run
View last scan results
node ${VULN_SCANNER_HOME:-$HOME/projects/vuln-scanner}/report.cjs
Cron
Weekly on Sundays at 09:00: scans all projects with package.json in $HOME/projects/
Config
${VULN_SCANNER_HOME:-$HOME/projects/vuln-scanner}/config.json
Adding projects without package.json in $HOME/projects/
node ${VULN_SCANNER_HOME:-$HOME/projects/vuln-scanner}/add-project.cjs --path ~/projects/ --manager npm
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.
- 4d ago First seen · 40 lines · 46 tokens per session scan A 985b304311cb
vuln-scanner is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 314 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-09-03.
Other skills, from other repositories
vulnerability-scanner
A security scanner that checks software dependencies for known vulnerabilities, analyzes whether they can be reached, creates a software bill of materials, and audits licenses.
software-dependency-audit
Perform a security audit on a package-lock.json file to identify HIGH and CRITICAL severity vulnerabilities, then write structured results to a CSV file.
dast-nuclei
Fast, template-based vulnerability scanning using ProjectDiscovery's Nuclei with extensive community templates covering CVEs, OWASP Top 10, misconfigurations, and security issues across web applications, APIs, and infrastructure. Use when: (1) Performing rapid vulnerability scanning with automated CVE detection, (2)…
container-grype
Container vulnerability scanning and dependency risk assessment using Grype with CVSS severity ratings, EPSS exploit probability, and CISA KEV indicators. Use when: (1) Scanning container images and filesystems for known vulnerabilities, (2) Integrating vulnerability scanning into CI/CD pipelines with severity…
dotnet-vuln-scanner
.NET dependency vulnerability scanner for NuGet packages, referenced DLL files, and dependency versions in configuration files. It checks them against CVE and GHSA security advisories.
nuclei-scan
Scan targets for vulnerabilities using Nuclei template-based scanner. Use when vulnerability assessment is needed, when scanning for CVEs or misconfigurations, when security testing web applications, APIs, or infrastructure, or when validating security findings.