A tool for retrieving information about Jira tickets, which are tracked work items in the Jira project-management system. It can fetch a ticket’s summary, type, and description.

Use it when naming branches, creating pull requests, or understanding what a Jira ticket requires.

It removes the need to copy ticket details manually before starting related development work. The retrieved context can clarify requirements and naming.

jira-ticket — Skill for Claude Code by flurdy

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 flurdy/agent-skills --skill jira-ticket

Clone the repo

git clone --depth 1 https://github.com/flurdy/agent-skills

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/flurdy/agent-skills/jira-ticket/github.svg)](https://agentmods.dev/skills/flurdy/agent-skills/jira-ticket)

Your own site

<a href="https://agentmods.dev/skills/flurdy/agent-skills/jira-ticket"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/jira-ticket/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/flurdy/agent-skills/jira-ticket"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/jira-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 620 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.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.00620
Opus 5	$0.00016	$0.00310
Sonnet 5	$0.00007	$0.00124
Haiku 4.5	$0.00003	$0.00062

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

Security

Grade A, and why

jira-ticket 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 9d 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.

skills/jira-ticket/SKILL.md · 82 lines

How it starts

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

Jira Ticket Lookup

Fetch details about a Jira ticket.

Requirements

This skill requires the mcp-server-atlassian-jira MCP server configured with the name jira.

Usage

/jira-ticket SP-123

Instructions

1. Look Up the Jira Ticket

Use the Jira MCP tools to fetch the ticket details:

mcp__jira__jira_get with:
  path: /rest/api/3/issue/{ticketNumber}
  jq: "{key: key, summary: fields.summary, type: fields.issuetype.name, description: fields.description}"

If mcp__jira__jira_get is not yet loaded (common on the first prompt of a session — MCP tools are deferred until first referenced), don't bail out. Instead:

Call ToolSearch with query: "select:mcp__jira__jira_get" to load its schema.
Retry the mcp__jira__jira_get call.
If ToolSearch returns no match — the jira MCP server is not configured for this project, not just lazy-loaded. Tell the user, and either:
- Ask them to paste the ticket summary/description so you can still infer the branch prefix, or
- Point them at the parent project's ~/.claude.json mcpServers.jira block if they want to copy it across (do not edit ~/.claude.json without explicit consent).

Treat a missing MCP server as "ask the user," not as a hard failure.

2. Determine Branch Prefix

Map the Jira issue type to a conventional commit prefix:

Issue Type	Branch Prefix
Story	`feat`
Task	`feat`
Bug	`fix`
Spike	`chore`
Sub-task	inherit from parent, or `feat`
Improvement	`feat`
Technical Debt	`refactor`
Documentation	`docs`
Default	`feat`

3. Return Ticket Info

Provide the user with:

Ticket key (e.g., SP-123)
Summary
Issue type
Suggested branch prefix based on type
Description (if available and requested)

Example Output

Ticket: SP-123
Summary: Add user authentication
Type: Story
Suggested prefix: feat
Branch name: feat/SP-123-add-user-authentication

Read the full file on GitHub · 82 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.

9d ago First seen · 82 lines · 33 tokens per session scan A aa08632b5bd7

Subscribe to this mod's changes

jira-ticket is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 620 once invoked, about $0.0002 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-31.

Project management agent-skills claude codex

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

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens