ai-dial-chat: Skill for Claude Code

.claude/skills/dep-triage/SKILL.md

dep-triage is a skill for Claude Code from epam/ai-dial-chat. It costs 53 tokens per session (1,630 once invoked), scanned A, original, Apache-2.0.

A review step for dependency-scan findings, such as reported software vulnerabilities. It checks each finding against how the dependency is actually used in the repository.

In plain words
What is it for?
Use it after a dependency scan to classify each reported CVE as confirmed or false positive and record the reason.
Why use it?
Automated scanners can report risks that are not exploitable in a particular codebase. This step separates confirmed risks from false positives before human review.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is epam/ai-dial-chat's own configuration. It tells Claude Code how to work on ai-dial-chat itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-dial-chat configures →

Reuse

Borrowing it

Nothing to install: this file belongs to epam/ai-dial-chat. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/epam/ai-dial-chat/development/.claude/skills/dep-triage/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/epam/ai-dial-chat

Made for: Claude Code.

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

agentmods badge for dep-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/epam/ai-dial-chat/dep-triage/github.svg)](https://agentmods.dev/skills/epam/ai-dial-chat/dep-triage)
Your own site
<a href="https://agentmods.dev/skills/epam/ai-dial-chat/dep-triage"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-chat/dep-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.

agentmods 80×15 button for dep-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/epam/ai-dial-chat/dep-triage"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-chat/dep-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,630 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00053 $0.01630
Opus 5 $0.00026 $0.00815
Sonnet 5 $0.00011 $0.00326
Haiku 4.5 $0.00005 $0.00163

Measured 10d ago against content hash a17f14a06714, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

dep-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 10d 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.

.claude/skills/dep-triage/SKILL.md · 178 lines

How it starts

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

Dependency Triage

Overview

Reads upstream scan findings, evaluates each in the repo's actual usage context, and emits the same findings augmented with triage_outcome (confirmed | false_positive) and a one-sentence triage_reason.

This is the triage step — does not run scanners itself. Always downstream of /dep-scan (or another scan agent emitting the same finding shape: cve, package, installed_version, fixed_version).

When to use

  • After /dep-scan in a chained agent (needs: [scan-deps]).
  • Whenever raw scanner output needs filtering before human review.
  • Periodically (e.g., scheduled re-triage to update prior-run outcomes as the codebase evolves).

Required tools

  • Read, Grep, Glob — to inspect repo source for package usage
  • Bash(git diff:*) — to scope which dependencies the PR touched
  • Skill — invocation only
  • Write — auto-granted; for stage-output.json

Inputs

  • upstream/scan-deps/stage-output.json — scan findings from the upstream scan-deps agent (or compatible scanner)

Triage rubric

For each finding under payload.findings[]:

Confirmed (triage_outcome: confirmed)

Mark confirmed if all three hold:

  1. The package is imported by repo source under apps/, libs/, or packages/.
  2. The vulnerable code path is plausibly reachable from a request, user input, or build output.
  3. The package is NOT exclusively a dev-time dependency.

False positive (triage_outcome: false_positive)

Mark FP if any one of these holds:

  1. Not a runtime dep. Listed only under devDependencies / peerDependencies and not exposed at build/runtime (test fixtures, type generators, bundler internals).
  2. Vulnerable function unused. The specific CVE-affected function/API is not called anywhere in apps/, libs/, or packages/.
  3. Network/host context excludes risk. E.g., DoS vuln on internal service the project doesn't expose; SSRF on URL the project never constructs; XSS in a sanitizer the project doesn't reach.
  4. Already mitigated transitively. Repo's package overrides / resolutions pin a safe version.
  5. Out-of-scope target. Scanner flagged a vendored binary, build artifact, or test fixture not part of the deployed application.

Read the full file on GitHub · 178 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. 10d ago First seen · 178 lines · 53 tokens per session scan A a17f14a06714

Subscribe to this mod's changes

dep-triage is a skill published in the GitHub repository epam/ai-dial-chat (504 stars, last pushed today), licensed Apache-2.0. It adds 53 tokens to every session and 1,630 once invoked, about $0.0003 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.