arn-code-batch-cve-fix

A workflow for applying fixes to groups of previously triaged CVEs, which are publicly recorded software security flaws. It prepares separate pull requests, meaning proposed code changes for review, for the configured security branch.

In plain words
What is it for?
Use it to patch grouped dependency vulnerabilities, create one pull request per group, and optionally archive fully resolved security plans.
Why use it?
It organizes dependency security work into isolated, reviewable changes instead of mixing many updates together. It requires human review when each change is created.

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/appsvortex/arness/arn-code-batch-cve-fix
Any agent
npx skills add AppsVortex/arness --skill arn-code-batch-cve-fix
Clone the repo
git clone --depth 1 https://github.com/AppsVortex/arness

Made for: Claude Code, Codex.

Per session 226 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,144 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.00226 $0.03144
Opus 5 $0.00113 $0.01572
Sonnet 5 $0.00045 $0.00629
Haiku 4.5 $0.00023 $0.00314

Measured yesterday against content hash 6c535d5ee539, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

arn-code-batch-cve-fix 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 yesterday.

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.

plugins/arn-code/skills/arn-code-batch-cve-fix/SKILL.md · 206 lines

How it starts

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

Arness Batch CVE Fix

Apply per-group fixes for previously-triaged CVEs, open per-group pull requests targeting the configured Security branch:, and optionally archive fully-resolved past CVE proposals. This skill consumes the triage records, sub-issue numbers, and parent-issue handle produced by arn-code-batch-cve-scan and dispatches one worker per group inside a pre-created git worktree.

Key architectural constraint: This skill is a sequencer — it MUST NOT duplicate sub-reference logic. All procedural detail lives in references/. Worker isolation (worktree setup, isolation check, cleanup-on-failure) is INHERITED from arn-code-batch-implement/references/worker-instructions.md — this skill's own worker-instructions.md DELEGATES to that source-of-truth and documents only the per-group fix scope.

Interactive-only (per spec FR §30). There is no --mode= argument. There is no proposal artifact. There is no headless / scheduled fix path. Every PR is human-reviewed at creation time; every past-plan archive is confirmed via AskUserQuestion. The auto-apply boundary (see references/auto-apply-boundary.md) controls whether the worker drives the dependency bump itself (when all 5 conditions are met) or pauses for human application — the worker still always opens a PR for review.

Pipeline position:

arn-code-batch-cve-scan (triage records + parent + sub-issues)
                  │
                  ▼
        **arn-code-batch-cve-fix**
        ┌─────────┴────────────┐
        │ form groups          │
        │ apply auto-apply gate│
        │ dispatch workers     │
        │ open per-group PRs   │
        │ post-fix cleanup     │
        └──────────────────────┘
                  │
                  ▼
        Per-group PRs targeting <Security branch>
        (each PR contains `Closes #N` per sub-issue)
                  │
                  ▼ (after merge — polled or --cleanup-resolved)
        Past-plan cleanup (interactive archive of resolved CVE_<ts>/)

Read the full file on GitHub · 206 lines

Files

What ships with it

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

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. yesterday First seen · 206 lines · 226 tokens per session scan A 6c535d5ee539

Subscribe to this mod's changes

arn-code-batch-cve-fix is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed 1mo ago), licensed MIT. It adds 226 tokens to every session and 3,144 once invoked, about $0.0011 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.