fetch-jira-issue

fetch-jira-issue is a skill for Claude Code from openshift-eng/ai-helpers. It costs 22 tokens per session (1,884 once invoked), scanned A, original, Apache-2.0.

A tool that retrieves detailed Red Hat JIRA issue information, including status, owner, comments, priority, linked pull requests, and progress. JIRA is a system for tracking software bugs and work items.

In plain words
What is it for?
Use it to investigate bugs linked to regressions, review recent activity, find related pull requests, and assess current ownership and progress.
Why use it?
It helps determine whether an issue is actively moving, stalled, or needs attention without manually checking its history.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ci plugin — 34 skills, 21 commands, 2 agents shipped together

Good fit Use it to investigate bugs linked to regressions, review recent activity, find related pull requests, and assess current ownership and progress.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/openshift-eng/ai-helpers/fetch-jira-issue
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 fetch-jira-issue
Clone the repo
git clone --depth 1 https://github.com/openshift-eng/ai-helpers

Made for: Claude Code.

Or install ci, the plugin that ships this one along with the rest of its 34 skills, 21 commands, 2 agents.

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 fetch-jira-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/fetch-jira-issue.svg)](https://agentmods.dev/skills/openshift-eng/ai-helpers/fetch-jira-issue)
Your own site
<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/fetch-jira-issue"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/fetch-jira-issue.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,884 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00022 $0.01884
Opus 5 $0.00011 $0.00942
Sonnet 5 $0.00004 $0.00377
Haiku 4.5 $0.00002 $0.00188

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

Security

Grade A, and why

fetch-jira-issue scanned grade A with 1 finding 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 9d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (fetch_jira_issue.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Check: `curl -s -o /dev/null -w '%{http_code}' https://redhat.atlassian.net`
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/ci/skills/fetch-jira-issue/SKILL.md · 218 lines

How it starts

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

Fetch JIRA Issue

This skill fetches detailed information about a JIRA issue from the Red Hat JIRA REST API. It retrieves status, assignee, priority, resolution, comments, linked PRs, and classifies the issue's progress as ACTIVE, STALLED, or NEEDS_ATTENTION.

When to Use This Skill

Use this skill when you need to:

  • Check the status and progress of a JIRA bug linked to a regression triage
  • Determine if a bug is being actively worked on or needs attention
  • Extract PR links from JIRA comments
  • Get assignee and component information for a JIRA issue
  • Analyze recent comment activity on a bug

Prerequisites

  1. JIRA API Token: Required for authentication

  2. Network Access: Must be able to reach redhat.atlassian.net

    • Check: curl -s -o /dev/null -w '%{http_code}' https://redhat.atlassian.net
  3. Python 3: Python 3.6 or later

    • Check: python3 --version
    • Uses only standard library (no external dependencies)

Implementation Steps

Step 1: Run the Python Script

# Path to the Python script
script_path="plugins/ci/skills/fetch-jira-issue/fetch_jira_issue.py"

# Fetch issue data in JSON format (default)
python3 "$script_path" OCPBUGS-74401 --format json

# Or fetch as human-readable summary
python3 "$script_path" OCPBUGS-74401 --format summary

# Pass token explicitly instead of using JIRA_API_TOKEN env var
python3 "$script_path" OCPBUGS-74401 --token "your-token" --format json

Step 2: Parse the Output

The script outputs structured JSON data that can be further processed:

# Store result in variable
jira_data=$(python3 "$script_path" OCPBUGS-74401 --format json)

# Extract key fields
status=$(echo "$jira_data" | jq -r '.status')
assignee=$(echo "$jira_data" | jq -r '.assignee.display_name // "Unassigned"')
progress_level=$(echo "$jira_data" | jq -r '.progress.level')
progress_reason=$(echo "$jira_data" | jq -r '.progress.reason')

# Check progress classification
echo "Status: $status"
echo "Assignee: $assignee"
echo "Progress: $progress_level - $progress_reason"

Read the full file on GitHub · 218 lines

Files

What ships with it

2 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. 9d ago First seen · 218 lines · 22 tokens per session scan A a6c4005b1319

Subscribe to this mod's changes

fetch-jira-issue is a skill published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed 4d ago), licensed Apache-2.0. It adds 22 tokens to every session and 1,884 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens