fix-security-issue

A guide for handling CVE reports, which are public records of known software security flaws, from security-checking tools.

In plain words
What is it for?
Use it to respond to vulnerability findings from tools such as Trivy or OSV-Scanner.
Why use it?
It helps decide whether to upgrade a vulnerable dependency, safely ignore a report, or ask before disabling an unmaintained checker.

Skill for Claude CodeCodex

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 skills/oxsecurity/megalinter/fix-security-issue
Any agent
npx skills add oxsecurity/megalinter --skill fix-security-issue
Clone the repo
git clone --depth 1 https://github.com/oxsecurity/megalinter

Made for: Claude Code, Codex.

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,880 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00059 $0.01880
Opus 5 $0.00030 $0.00940
Sonnet 5 $0.00012 $0.00376
Haiku 4.5 $0.00006 $0.00188

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

Security

Grade A, and why

fix-security-issue 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.

.claude/skills/fix-security-issue/SKILL.md · 131 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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 · 131 lines · 59 tokens per session scan A 807e8865bb5c

Subscribe to this mod's changes

fix-security-issue is a skill published in the GitHub repository oxsecurity/megalinter (2,576 stars, last pushed today), licensed AGPL-3.0. It adds 59 tokens to every session and 1,880 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.