agentmods.dev

jira-cve-extraction

jira-cve-extraction is a skill for Claude Code from openshift-eng/ai-helpers. It costs 51 tokens per session (3,606 once invoked), scanned A, original, Apache-2.0.

A helper that reads a Jira issue—a work item in Jira—and extracts the CVE, image name, branch, and security details needed for a vulnerability analysis. A CVE is a public identifier for a known software vulnerability.

In plain words
What is it for?
Use it when a CVE analysis starts from one Jira ticket or a Jira search, especially when the ticket identifies a container image and source branch.
Why use it?
It removes manual copying from security tickets into the analysis process and provides the surrounding context, such as severity, affected versions, and workarounds.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the compliance plugin — 9 skills, 1 command shipped together

not rated 121repo +2 changed 23d ago A scan 51 tokens original Apache-2.0

Good fit Use it when a CVE analysis starts from one Jira ticket or a Jira search, especially when the ticket identifies a container image and source branch.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/openshift-eng/ai-helpers/jira-cve-extraction
View source ↗ openshift-eng/ai-helpers openshift-eng.github.io
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.

Any agent
npx skills add openshift-eng/ai-helpers --skill jira-cve-extraction
Clone the repo
git clone --depth 1 https://github.com/openshift-eng/ai-helpers

Made for: Claude Code.

Or install compliance, the plugin that ships this one along with the rest of its 9 skills, 1 command.

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 jira-cve-extraction

README.md
[![agentmods](https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/jira-cve-extraction/github.svg)](https://agentmods.dev/skills/openshift-eng/ai-helpers/jira-cve-extraction)
Your own site
<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/jira-cve-extraction"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/jira-cve-extraction/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 jira-cve-extraction

Your own site · 80×15
<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/jira-cve-extraction"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/jira-cve-extraction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,606 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.
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.00051 $0.03606
Opus 5.5 $0.00020 $0.01442
Sonnet 5.5 $0.00010 $0.00721
Haiku 4.5 $0.00005 $0.00361

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

Security

Grade A, and why

jira-cve-extraction 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 23d 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.

plugins/compliance/skills/jira-cve-extraction/SKILL.md · 285 lines

How it starts

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

Jira CVE Extraction

Fetches a Jira ticket and extracts three things:

  1. CVE ID — passed to Phase 1 (cve-intelligence-gathering)
  2. Image name — passed to Phase 0.7 via the image-repo-mapping skill to resolve which repo to clone
  3. Enriched context — CVSS, CWE, priority, target versions, workarounds — embedded in the Phase 3 report and used to seed the CVE profile

Key insight: Security tracking tickets (e.g. OCPBUGS CVE trackers) follow a consistent summary format: CVE-YYYY-NNNNN <component>: <description> [<version>]. Parsing the summary is the most reliable single extraction path and should always be tried first — it typically yields the CVE ID, image name, and branch in one step.

When to Use This Skill

Use this skill when the user invokes /compliance:analyze-cve with --jira=PROJ-NNN or --jql="...".

Prerequisites

Preferred: Atlassian MCP

Use the Atlassian Rovo MCP tools bundled with the jira plugin (or an equivalent Atlassian MCP server configured for this Claude Code instance):

  • getJiraIssue — fetch a single ticket
  • searchJiraIssuesUsingJql — fetch a batch of tickets (Phase 0.3 / idempotency lookups)
  • editJiraIssue — update labels (idempotency marker)

Fallback: jira-cli

If the MCP server is unavailable: jira issue get <TICKET> and jira issue edit <TICKET> --label ... (from go-jira). Requires ~/.jira.d/config.yml configured for the target Jira instance.

Credential rule: Never print, echo, or log any token, password, or key value — not in shell commands, not in model responses, not in debug output. Reference credentials only via environment variable names (e.g. $JIRA_API_TOKEN).

Implementation Steps

Step 1: Validate Ticket Format

PROJECT-NNNNN   e.g. OCPBUGS-12345, CNTRLPLANE-678

Pattern: ^[A-Z]+-[0-9]+$

  • IF invalid → Return error: "Invalid Jira ticket format. Expected PROJECT-NNNNN."
  • IF valid → Continue

Step 2: Fetch the Ticket

Read the full file on GitHub · 285 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. 23d ago Changed f827db4be00e
  2. 1mo ago First seen · 285 lines · 51 tokens per session scan A 65e45327b792

Subscribe to this mod's changes

jira-cve-extraction is a skill published in the GitHub repository openshift-eng/ai-helpers (121 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 3,606 once invoked, about $0.0002 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-09-11.

Security
Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens