agentmods.dev

fetch_jira_requirements

fetch_jira_requirements is a command for Claude Code from anhtester/claude-testing-kit. It costs 17 tokens per session (770 once invoked), scanned A, original, MIT.

A Jira retrieval command that reads requirements, user stories, or issues from Jira and saves them as Markdown or JSON files.

In plain words
What is it for?
It helps fetch one Jira issue, issues from a project and type, results matching a JQL query, or child issues of an epic.
Why use it?
It removes the need to copy ticket details by hand when preparing documentation or test automation.

Command for Claude Code

not rated 50 26d ago A scan 17 tokens original MIT
View the source file anhtester/claude-testing-kit
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 commands/anhtester/claude-testing-kit/fetch_jira_requirements
Clone the repo
git clone --depth 1 https://github.com/anhtester/claude-testing-kit

Made for: Claude Code.

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_requirements

README.md
[![agentmods](https://agentmods.dev/badge/commands/anhtester/claude-testing-kit/fetch_jira_requirements.svg)](https://agentmods.dev/commands/anhtester/claude-testing-kit/fetch_jira_requirements)
Your own site
<a href="https://agentmods.dev/commands/anhtester/claude-testing-kit/fetch_jira_requirements"><img src="https://agentmods.dev/badge/commands/anhtester/claude-testing-kit/fetch_jira_requirements.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 770 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.00017 $0.00770
Opus 5 $0.00009 $0.00385
Sonnet 5 $0.00003 $0.00154
Haiku 4.5 $0.00002 $0.00077

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

Security

Grade A, and why

fetch_jira_requirements 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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/commands/fetch_jira_requirements.md · 61 lines

How it starts

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

Workflow: Fetch Jira Requirements

BẮT BUỘC (MANDATORY SKILL): Bạn PHẢI nạp và đọc kỹ nội dung của skill skills-jira-integration (tại .claude/skills/skills-jira-integration/SKILL.md) để biết cách sử dụng scripts trước khi bắt đầu.

Workflow này giúp lấy requirements, user stories, hoặc issues từ Jira và chuyển thành tài liệu phục vụ test automation.

Các bước thực hiện:

  1. Kiểm tra prerequisites:

    • Đọc skill skills-jira-integration để nắm cấu trúc scripts.
    • Kiểm tra file .env đã tồn tại và được cấu hình đúng.
    • Kiểm tra dependencies đã được cài đặt (scripts/integrations/node_modules/).
    • Nếu chưa cài, chạy: cd scripts/integrations && npm install

  2. Xác định thông tin cần lấy:

    • Hỏi user cung cấp thông tin:
      • Issue key cụ thể (VD: PROJ-123) → dùng --issue
      • Project key + Issue type (VD: PROJ, Story) → dùng --project --type
      • JQL query tùy chỉnh → dùng --jql
      • Epic key (lấy children) → dùng --epic
    • Xác định format output: json (default) hoặc md (markdown requirement)

  3. Thực thi script:

    • Chạy lệnh phù hợp:
    # Lấy 1 issue cụ thể
node scripts/integrations/jira/jira_fetcher.js --issue <ISSUE_KEY>

# Lấy issues theo project
node scripts/integrations/jira/jira_fetcher.js --project <PROJECT_KEY> --type <TYPE> --max <N>

# Tìm theo JQL
node scripts/integrations/jira/jira_fetcher.js --jql "<JQL_QUERY>"

# Xuất Markdown
node scripts/integrations/jira/jira_fetcher.js --issue <KEY> --format md --output ./requirements/jira

  4. Xử lý kết quả:

    • Kiểm tra output file được tạo trong requirements/jira/ (hoặc --output chỉ định).
    • Nếu format json: Đọc và hiển thị tóm tắt issues cho user.
    • Nếu format md: Hiển thị nội dung markdown requirement cho user review.
    • Nếu gặp lỗi: Đọc log, phân tích nguyên nhân theo bảng Troubleshooting trong skill.

  5. Xử lý lỗi thường gặp:

    • HTTP 401: Token sai → hướng dẫn user kiểm tra JIRA_API_TOKEN hoặc JIRA_PAT
    • HTTP 404: Issue không tồn tại hoặc JIRA_BASE_URL sai
    • File .env not found: Hướng dẫn user copy .env.example → .env
    • Module not found: Chạy npm install trong scripts/integrations/

Read the full file on GitHub · 61 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. 4d ago First seen · 61 lines · 17 tokens per session scan A 458ccf855c99

Subscribe to this mod's changes

fetch_jira_requirements is a command published in the GitHub repository anhtester/claude-testing-kit (50 stars, last pushed 26d ago), licensed MIT. It adds 17 tokens to every session and 770 once invoked, about $0.0001 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.

Project managementaitestinganhtesterclaude-codeclaudetestingkittest-automationtest-manual
Related

Other commands, from other repositories

fetch_jira_requirements

Lấy Requirements / User Stories từ Jira ticket và lưu thành file markdown hoặc JSON.

anhtester/ClaudeCode_Playwright_Demo · 17 tokens

project-recap

Generate a visual project recap for context switching.

nicobailon/visual-explainer · 12 tokens

os-meeting

快速创建和管理AI团队会议.

CronusL-1141/AI-company · 11 tokens

standup

Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.

skullninja/coco-workflow · 21 tokens

m-task-planner

Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).

penwyp/ClaudePreference · 0 tokens

triage

Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.

jschuller/mcp-server-servicenow · 22 tokens