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.
curl -O https://raw.githubusercontent.com/epam/ai-dial-chat/development/.claude/skills/fix-cve-backport/SKILL.mdgit clone --depth 1 https://github.com/epam/ai-dial-chatWrote 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/epam/ai-dial-chat/fix-cve-backport)<a href="https://agentmods.dev/skills/epam/ai-dial-chat/fix-cve-backport"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-chat/fix-cve-backport/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.
<a href="https://agentmods.dev/skills/epam/ai-dial-chat/fix-cve-backport"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-chat/fix-cve-backport.svg" alt="Reviewed on agentmods" width="80" 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.00070 | $0.02680 |
| Opus 5.5 | $0.00028 | $0.01072 |
| Sonnet 5.5 | $0.00014 | $0.00536 |
| Haiku 4.5 | $0.00007 | $0.00268 |
Grade A, and why
fix-cve-backport 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix CVEs and backport to two releases
Discover vulnerabilities when no advisory is supplied, then prepare focused fixes
on development and independently validated backports to
the two highest numeric release-X.Y branches on the chosen remote. Published
releases, tags, commit dates, and local branch availability do not choose targets.
Discover the names on every run; never hardcode today's release versions.
Scope and execution
- Accept CVE/GHSA identifiers, scanner findings, a package/image report, or an existing fix commit/PR. Reuse supplied details and ticket numbers. With no finding supplied, run automatic discovery after establishing branch snapshots; do not ask the user to provide a CVE identifier. With explicit findings, stay within that scope unless the user also requests a broader scan.
- A request to fix and backport authorizes topic branches, local commits, and cherry-picks. Complete these without another confirmation. A preview/plan-only or scan-only request produces a report without fixes, commits, or publication. Honor explicitly supplied source/target branches.
- Push and PR creation follow the user's requested scope. If requested, finish
them without reconfirming. Otherwise finish with local branches/commits. Never
merge, tag a release, publish an image, or push directly to development/release
branches as part of this workflow. Topic names start with
fix/orbackport/. - Keep unrelated edits intact. Work in separate worktrees with unique paths and branches. Inspect existing worktrees before reusing one; never stash, reset, clean, delete, or amend another task's work.
1. Establish branch snapshots
Read the repository's AGENTS.md and relevant path rules. For AI DIAL Chat, read
references/ai-dial-chat.md for repository pitfalls.
Determine the Git root, intended remote, current worktrees, and working-tree
status. Default to origin when it is the repository's upstream; distinguish a
fork's push remote from the authoritative remote containing release branches.
What ships with it
4 files 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.
- today First seen · 217 lines · 70 tokens per session scan A b0df13b1b6cb
fix-cve-backport is a skill published in the GitHub repository epam/ai-dial-chat (502 stars, last pushed today), licensed Apache-2.0. It adds 70 tokens to every session and 2,680 once invoked, about $0.0003 per session on Opus 5.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-10-23.
Other skills, from other repositories
release-notes
Use when the user asks to enhance, refine, polish, or "look at" the release notes for a tag of @epam/ai-dial-ui-kit — typically a freshly cut stable release (e.g. 0.11.0). Reads the CI-generated notes off the GitHub release, classifies and rewrites each bullet in this project's editorial voice, and saves a draft to…
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
otto-drive-pr
PR mergeability, CI, and live preview.
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…