Fetch JIRA Issue

Fetch JIRA Issue is a skill for Claude Code, Codex from wangke19/gemini-ai-helpers. It costs 21 tokens per session (1,883 once invoked), scanned A, a copy of fetch-jira-issue, Apache-2.0.

A tool for retrieving detailed issue records from JIRA, a system teams use to track bugs and other work.

In plain words
What is it for?
Use it to check regression bugs, find pull-request links in comments, review recent activity, and classify issues as active, stalled, or needing attention.
Why use it?
It gathers the issue's current state, ownership, discussion, related pull requests, and progress in one result, helping reveal whether work is active or stalled.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to check regression bugs, find pull-request links in comments, review recent activity, and classify issues as active, stalled, or needing attention.

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

Made for: Claude Code, Codex.

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/wangke19/gemini-ai-helpers/fetch-jira-issue/github.svg)](https://agentmods.dev/skills/wangke19/gemini-ai-helpers/fetch-jira-issue)
Your own site
<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/fetch-jira-issue"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/fetch-jira-issue/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 Fetch JIRA Issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/fetch-jira-issue"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/fetch-jira-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,883 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.
Origin 100% copy Near-identical to another mod 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.00021 $0.01883
Opus 5 $0.00010 $0.00941
Sonnet 5 $0.00004 $0.00377
Haiku 4.5 $0.00002 $0.00188

Measured 12d ago against content hash 36e8d93a8e2e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 12d 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

This is a copy

100% identical to fetch-jira-issue — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

extensions/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="extensions/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. 12d ago First seen · 218 lines · 21 tokens per session scan A 36e8d93a8e2e

Subscribe to this mod's changes

Fetch JIRA Issue is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,883 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to fetch-jira-issue, differing in 4 lines, and is treated as a copy.