vulnerabilities

A deep security scan for a software project. It checks source code, dependencies, repository files, and TLS settings for secrets, insecure patterns, known vulnerabilities, and related risks.

In plain words
What is it for?
Use it to scan a project or path for hardcoded secrets, insecure code, TLS bypasses, vulnerable packages, tracked environment files, and key or certificate files.
Why use it?
It brings several security checks into one report and includes remediation guidance, helping identify issues such as exposed keys, SQL injection, cross-site scripting, and dependency CVEs.

Command

Install

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.

agentmods
npx agentmods add commands/vyuh-labs/dxkit/vulnerabilities
Clone the repo
git clone --depth 1 https://github.com/vyuh-labs/dxkit
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,008 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01008
Opus 5 $0.00000 $0.00504
Sonnet 5 $0.00000 $0.00202
Haiku 4.5 $0.00000 $0.00101

Measured 2d ago against content hash 0c30505f0c38, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vulnerabilities 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.

docs/commands/vulnerabilities.md · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.

vyuh-dxkit vulnerabilities

Run as: vyuh-dxkit <cmd> after npm install -g @vyuhlabs/dxkit, or npx @vyuhlabs/dxkit <cmd> for one-shot use. Examples on this page use the short form.

Deep security scan. Aliases: vuln. Produces a complete security report — secrets, code patterns, dependency CVEs, TLS bypasses, and remediation guidance.

Usage

vyuh-dxkit vulnerabilities [path] [options]
vyuh-dxkit vuln [path]  # alias

What gets scanned

Source Tool What it finds
Secrets in source gitleaks (800+ patterns) hardcoded API keys, JWTs, private keys, etc.
Static code patterns semgrep p/security-audit ruleset eval, SQLi, XSS, SSRF, CORS misconfig, more
TLS bypass idioms per-pack regex (registry-driven) rejectUnauthorized: false, InsecureSkipVerify: true, OpenSSL::SSL::VERIFY_NONE, etc.
Dependency CVEs npm-audit, pip-audit, osv-scanner, govulncheck, cargo-audit, depending on the active pack upstream advisories with CVSS, KEV, EPSS enrichment
Repo artifacts find/git .env tracked in git, .key/.pem files on disk

Options

Option Effect
--detailed Write the detailed report + JSON
--json Stdout JSON
--no-save Skip writing files
--graph-context Attach each finding's module + blast radius to the detailed report (needs a graph; fail-open — see context)
--attribute Attach a "Who to ask" column (git blame → active-owner model; inactive authors routed to the current owner). Opt-in; names + @handles, never emails. Historical only — net-new findings are introduced by your own change.

Read the full file on GitHub · 95 lines

Changes

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.

  1. 2d ago First seen · 95 lines · 0 tokens per session scan A 0c30505f0c38

Subscribe to this mod's changes

vulnerabilities is a command published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,008 tokens. 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-31.