Agent skill

Dep Scan

Runs Trivy filesystem scan against the repo root and emits structured vulnerability findings (CVE, package, versions) in the SDLC reviewer schema.

Apache-2.0Auto-check passedSecurity

Install Dep Scan

skills CLI

$ npx skills add epam/ai-dial-chat --skill dep-scan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install epam/ai-dial-chat dep-scan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/epam/ai-dial-chat.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/dep-scan .claude/skills/dep-scan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "dep-scan" agent skill from https://github.com/epam/ai-dial-chat/tree/development/.claude/skills/dep-scan into .claude/skills/dep-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dep-scan", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/epam/ai-dial-chat/tree/development/.claude/skills/dep-scan

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add epam/ai-dial-chat --skill dep-scan -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install epam/ai-dial-chat dep-scan --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/epam/ai-dial-chat.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/dep-scan .agents/skills/dep-scan && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "dep-scan" agent skill from https://github.com/epam/ai-dial-chat/tree/development/.claude/skills/dep-scan into .agents/skills/dep-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dep-scan", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add epam/ai-dial-chat --skill dep-scan -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install epam/ai-dial-chat dep-scan --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/epam/ai-dial-chat.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/dep-scan .cursor/skills/dep-scan && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "dep-scan" agent skill from https://github.com/epam/ai-dial-chat/tree/development/.claude/skills/dep-scan into .cursor/skills/dep-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dep-scan", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/epam/ai-dial-chat.git --path .claude/skills/dep-scan

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add epam/ai-dial-chat --skill dep-scan -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install epam/ai-dial-chat dep-scan --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/epam/ai-dial-chat.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/dep-scan .gemini/skills/dep-scan && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "dep-scan" agent skill from https://github.com/epam/ai-dial-chat/tree/development/.claude/skills/dep-scan into .gemini/skills/dep-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dep-scan", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install epam/ai-dial-chat dep-scan

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add epam/ai-dial-chat --skill dep-scan -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/epam/ai-dial-chat.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/dep-scan .github/skills/dep-scan && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "dep-scan" agent skill from https://github.com/epam/ai-dial-chat/tree/development/.claude/skills/dep-scan into .github/skills/dep-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dep-scan", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add epam/ai-dial-chat --skill dep-scan -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install epam/ai-dial-chat dep-scan --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/epam/ai-dial-chat.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/dep-scan .opencode/skills/dep-scan && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "dep-scan" agent skill from https://github.com/epam/ai-dial-chat/tree/development/.claude/skills/dep-scan into .opencode/skills/dep-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dep-scan", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: dep-scan
GitHub stars: 504
Token cost: ~1.2k tokens
SKILL.md length: 472 words
Files: 1
Skills in repo: 18
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Runs Trivy filesystem scan against the repo root and emits structured vulnerability findings (CVE, package, versions) in the SDLC reviewer schema.

Works in 5 steps: Run Trivy → Parse the report → Map each vulnerability to a finding → …
An agent needs to detect known CVEs in project dependencies for downstream triage
SKILL.md covers Overview, When to use, Required tools and Process, plus 2 more sections
Calls trivy

What it does

Dep Scan is an agent skill from epam/ai-dial-chat. Runs Trivy filesystem scan against the repo root and emits structured vulnerability findings (CVE, package, versions) in the SDLC reviewer schema. Use when an agent needs to detect known CVEs in project dependencies for downstream triage or human review.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Security, covering Vulnerability scanning. It works with Trivy and Bash. The repository describes itself as: A default UI for AI DIAL. The licence is Apache-2.0.

When your agent uses it

An agent needs to detect known CVEs in project dependencies for downstream triage
Tasks that involve Vulnerability scanning

Example prompts

“/dep-scan”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Run Trivy
Parse the report
Map each vulnerability to a finding
Set status
Write stage-output.json

What it can do on your machine

Read from SKILL.md and the folder at commit 2d66a8d. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- trivy
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dep Scan loads about 1.2k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 472 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~66
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from epam/ai-dial-chat at commit 2d66a8d, republished under its Apache-2.0 licence (© epam). 472 words, ~1,226 tokens.

Download SKILL.mdSave it as .claude/skills/dep-scan/SKILL.md (or your agent's skills folder).

name: dep-scan
description: Runs Trivy filesystem scan against the repo root and emits structured vulnerability findings (CVE, package, versions) in the SDLC reviewer schema. Use when an agent needs to detect known CVEs in project dependencies for downstream triage or human review.
disable-model-invocation: true

Dependency Scan (Trivy)

Overview

Filesystem scan for known CVEs. Trivy autodetects lockfiles (package-lock.json, pnpm-lock.yaml, etc.) and produces a JSON report; this skill parses that report and emits findings in the SDLC reviewer shape so downstream agents (e.g., /dep-triage) and human reviewers can consume them uniformly.

This is the scan step only — no triage, no false-positive analysis. That happens downstream.

When to use

PR-time dependency check (chained before /dep-triage).
Scheduled dependency scans (nightly, weekly).
Any flow needing machine-readable vulnerability output that another agent or process will consume.

Required tools

Bash(trivy:*) — to invoke the CLI
Write — to produce stage-output.json (auto-granted by the platform)
Read, Glob — to inspect lockfiles or scan output if needed

Process

1. Run Trivy

Filesystem scan from repo root, JSON output, medium severity and above. Use Trivy's --output flag, not shell redirection (>) — Claude Code's Bash tool rejects shell-redirection operators and would deny the command:

bash

trivy fs --format json --severity HIGH,CRITICAL,MEDIUM --quiet --output /tmp/trivy.json .

Same effect: writes report to /tmp/trivy.json. No >, no |, no shell-variable expansion — exactly what Bash(trivy:*) allows.

Notes:

--quiet suppresses interactive UI noise.
If /tmp/trivy.json is missing or zero-length after the command, treat it as a scanner failure (see Heuristics).

2. Parse the report

Use the Read tool to load /tmp/trivy.json into your reasoning context. Do NOT attempt to use cat, head, tail, jq, grep, awk, or any other shell command to inspect the file — those aren't in the agent's allowed_tools (only Bash(trivy:*) is) and the Bash tool will deny them, burning turns on retries. The Read tool is the intended path for inspecting on-disk JSON.

The file is on the order of tens-to-hundreds of KB; one Read call loads it cleanly.

Trivy's structure:

{
  "Results": [
    {
      "Target": "package-lock.json",
      "Type": "npm",
      "Vulnerabilities": [
        {
          "VulnerabilityID": "CVE-...",
          "PkgName": "lodash",
          "InstalledVersion": "4.17.20",
          "FixedVersion": "4.17.21",
          "Severity": "HIGH",
          "Title": "..."
        }
      ]
    }
  ]
}

A Result may have no Vulnerabilities array if the target is clean — skip it.

Show full SKILL.md (191 more words)Show less

3. Map each vulnerability to a finding

Lowercase severity; carry through CVE, package, versions:

{
  "severity": "high",
  "file": "package-lock.json",
  "message": "<CVE>: <Title>. Affected: <pkg>@<version>. Fixed in <fixed>.",
  "suggested_fix": "Upgrade <pkg> to >=<fixed>.",
  "cve": "<CVE>",
  "package": "<pkg>",
  "installed_version": "<installed>",
  "fixed_version": "<fixed>",
  "target_type": "<npm|gomod|...>"
}

The cve, package, installed_version, fixed_version, and target_type fields are the contract for /dep-triage — don't omit them.

4. Set status

passed — no findings at MEDIUM+
passed_with_findings — findings exist but all are MEDIUM (no HIGH/CRITICAL)
failed — any HIGH or CRITICAL finding

5. Write `stage-output.json`

Use the Write tool to save at the repo root. Include payload.scan_summary so downstream consumers don't have to recount:

{
  "stage": "scan-deps",
  "status": "<above>",
  "summary": "Trivy fs: <N> findings (<H> high, <M> medium).",
  "payload": {
    "scan_summary": {
      "total": <N>,
      "by_severity": { "critical": <c>, "high": <h>, "medium": <m> },
      "scanner": "trivy fs"
    },
    "findings": [ ... ]
  }
}

Heuristics

Scanner failure → high-severity finding. If trivy exits non-zero or /tmp/trivy.json is empty/malformed, emit one high-severity finding with file: null and message quoting the stderr verbatim, then set status: failed. Don't silently produce empty findings.
Truncate verbose descriptions. Trivy's Description field can be very long; keep it brief in the message field or move detail to cve lookups elsewhere.
Don't filter by reachability here. That's /dep-triage's job. Emit every CVE Trivy finds at the configured severity threshold.

Output for downstream

The exact shape above is the contract for /dep-triage. The triage skill keys off cve, package, and installed_version to look up usage in the repo. Omit those fields and triage degrades to "every finding marked confirmed."

Files

Just SKILL.md in .claude/skills/dep-scan of epam/ai-dial-chat.

Open the folder on GitHubat commit 2d66a8d

Compare with similar skills

Dep Scan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dep Scan compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Dep Scan this skillepam/ai-dial-chat	504	—	~1.2k	Automated safety check: Pass	Apache-2.0	today
Upgrade Java Depsnvuillam/npm-groovy-lint	248	—	~1.9k	Automated safety check: Notes	MIT	4 days ago
Fix Scan Findingmalloydata/publisher	116	—	~5.1k	Automated safety check: Pass	MIT	today
Security Vulnerabilities Patcheraxelixlabs/axelix	148	—	~4.2k	Automated safety check: Pass	LGPL-3.0	yesterday
Fix Image Cveskubernetes-sigs/cloud-provider-azure	294	—	~818	Automated safety check: Pass	Apache-2.0	today
Security ReviewerJeffallan/claude-skills	12k	—	~1.3k	Automated safety check: Pass	MIT	5 days ago

Similar skills

Upgrade Java Deps
nvuillam/npm-groovy-lint
Upgrade CodeNarc and the bundled Java dependencies (jackson, logback, slf4j, janino, GMetrics, Groovy libs) that ship inside lib/java/, rebuild the deterministic CodeNarcServer.jar, and verify…
248 GitHub stars~1.9k tokensUpdated 4 days ago
SecurityAuto-check: notes
Fix Scan Finding
malloydata/publisher
Fix a CRITICAL Trivy finding that is failing CI in this repo (a vulnerability, misconfiguration, or secret from security-scan.yml or image-scan.yml), or add, review, or retire an entry in…
116 GitHub stars~5.1k tokensUpdated today
SecurityAuto-check passed
Security Vulnerabilities Patcher
axelixlabs/axelix
Create batched Dependabot-style pull requests for GitHub security findings in axelixlabs/axelix, grouped by dependency surface such as master/front-end, master/build.gradle.kts, or starter Gradle…
148 GitHub stars~4.2k tokensUpdated yesterday
SecurityAuto-check passed
Fix Image Cves
kubernetes-sigs/cloud-provider-azure
Official
Scan a built container image with Trivy, classify fixable Go-module and base-image CVEs, apply dependency and Dockerfile fixes, and verify the result with file checks and an optional image rescan.
294 GitHub stars~818 tokensUpdated today
SecurityAuto-check passed
Security Reviewer
Jeffallan/claude-skills
Audits code and infrastructure for vulnerabilities and produces a severity-rated report with locations and remediation, using SAST, dependency and secrets scans plus manual review.
12k GitHub stars~1.3k tokensUpdated 5 days ago
SecurityAuto-check passed
Security Audit
Aedelon/claude-code-blueprint
Proactive security audit: OWASP top 10, dependency vulnerabilities, secrets detection, input validation, auth patterns, and secure defaults.
120 GitHub stars~1.6k tokensUpdated 7 mo ago
SecurityAuto-check: notes

Questions about Dep Scan

What does Dep Scan do?

Runs Trivy filesystem scan against the repo root and emits structured vulnerability findings (CVE, package, versions) in the SDLC reviewer schema. Dep Scan is an agent skill from epam/ai-dial-chat. Runs Trivy filesystem scan against the repo root and emits structured vulnerability findings (CVE, package, versions) in the SDLC reviewer schema.

When should I use Dep Scan?

Dep Scan fits situations like: an agent needs to detect known CVEs in project dependencies for downstream triage; tasks that involve Vulnerability scanning.

How do I install Dep Scan in Claude Code?

Run `npx skills add epam/ai-dial-chat --skill dep-scan -a claude-code`. Or copy the skill folder (.claude/skills/dep-scan in epam/ai-dial-chat) into .claude/skills/dep-scan in your project. Claude Code loads it when a task matches its description.

How do I install Dep Scan in Codex?

Run `npx skills add epam/ai-dial-chat --skill dep-scan -a codex`. Or copy the skill folder (.claude/skills/dep-scan in epam/ai-dial-chat) into .agents/skills/dep-scan in your project. Codex loads it when a task matches its description.

Can I use Dep Scan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add epam/ai-dial-chat --skill dep-scan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dep-scan, .gemini/skills/dep-scan, .github/skills/dep-scan and .opencode/skills/dep-scan in your project.

What does Dep Scan need to run?

Going by SKILL.md and its folder, Dep Scan needs the command-line tools its instructions call (trivy).

Does Dep Scan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Dep Scan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dep Scan use?

Dep Scan is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dep Scan use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dep Scan?

Skills that share tags, products or a category with Dep Scan: Upgrade Java Deps (nvuillam/npm-groovy-lint, 248 stars), Fix Scan Finding (malloydata/publisher, 116 stars), Security Vulnerabilities Patcher (axelixlabs/axelix, 148 stars) and Fix Image Cves (kubernetes-sigs/cloud-provider-azure, 294 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dep Scan?

epam (a GitHub organization) maintains it in epam/ai-dial-chat, which has 504 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

Source: epam/ai-dial-chat on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Dep Scan

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Dependency Scan (Trivy)

Overview

When to use

Required tools

Process

1. Run Trivy

2. Parse the report

3. Map each vulnerability to a finding

4. Set status

5. Write stage-output.json

Heuristics

Output for downstream

Files

Compare with similar skills

Similar skills

More from epam/ai-dial-chat

Related

Questions about Dep Scan

5. Write `stage-output.json`