A command for working with Jira, a system for tracking software tasks and issues. It retrieves tickets, analyzes their requirements, searches issues, adds comments, and changes status.

Extracting acceptance criteria and test scenarios, searching with JQL, posting structured updates, and moving tickets through workflow states.

It reduces the need to switch between the coding workflow and Jira when understanding work or reporting progress.

jira — Command for Claude Code by sifxprime/kodelyth-ecc

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.

Clone the repo

git clone --depth 1 https://github.com/sifxprime/kodelyth-ecc

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/commands/sifxprime/kodelyth-ecc/jira/github.svg)](https://agentmods.dev/commands/sifxprime/kodelyth-ecc/jira)

Your own site

<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/jira"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/jira/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/commands/sifxprime/kodelyth-ecc/jira"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/jira.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 893 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 89% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00027	$0.00893
Opus 5.5	$0.00011	$0.00357
Sonnet 5.5	$0.00005	$0.00179
Haiku 4.5	$0.00003	$0.00089

Measured 1mo ago against content hash 26cfdf55ec32, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jira 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 1mo 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

This is a copy

89% identical to jira — 20 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.

commands/jira.md · 123 lines

How it starts

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

Jira Command

Interact with Jira tickets directly from your workflow — fetch tickets, analyze requirements, add comments, and transition status.

Usage

/jira get <TICKET-KEY>          # Fetch and analyze a ticket
/jira comment <TICKET-KEY>      # Add a progress comment
/jira transition <TICKET-KEY>   # Change ticket status
/jira search <JQL>              # Search issues with JQL

What This Command Does

Get & Analyze — Fetch a Jira ticket and extract requirements, acceptance criteria, test scenarios, and dependencies
Comment — Add structured progress updates to a ticket
Transition — Move a ticket through workflow states (To Do → In Progress → Done)
Search — Find issues using JQL queries

How It Works

`/jira get <TICKET-KEY>`

Fetch the ticket from Jira (via MCP jira_get_issue or REST API)
Extract all fields: summary, description, acceptance criteria, priority, labels, linked issues
Optionally fetch comments for additional context
Produce a structured analysis:

Ticket: PROJ-1234
Summary: [title]
Status: [status]
Priority: [priority]
Type: [Story/Bug/Task]

Requirements:
1. [extracted requirement]
2. [extracted requirement]

Acceptance Criteria:
- [ ] [criterion from ticket]

Test Scenarios:
- Happy Path: [description]
- Error Case: [description]
- Edge Case: [description]

Dependencies:
- [linked issues, APIs, services]

Recommended Next Steps:
- /plan to create implementation plan
- /tdd to implement with tests first

`/jira comment <TICKET-KEY>`

Summarize current session progress (what was built, tested, committed)
Format as a structured comment
Post to the Jira ticket

`/jira transition <TICKET-KEY>`

Fetch available transitions for the ticket
Show options to user
Execute the selected transition

`/jira search <JQL>`

Execute the JQL query against Jira
Return a summary table of matching issues

Prerequisites

This command requires Jira credentials. Choose one:

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

1mo ago Changed · +16 lines 26cfdf55ec32
1mo ago First seen · 107 lines · 27 tokens per session scan A edf9d093c6fa

Subscribe to this mod's changes

jira is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 15d ago), licensed MIT. It adds 27 tokens to every session and 893 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to jira, differing in 20 lines, and is treated as a copy.

Claude Code Project management ai-agents antigravity automation claude coding-assistant

maintainer-standup

Synthesize the maintainer's morning standup brief from gathered git/PR/issue/state data.

coleam00/Archon · 19 tokens

hatch3r-roadmap

Sequence delivery phases over time into a dependency-ordered milestone plan with business and technical lenses, emitting a todo.md rollout schedule rather than design docs.

hatch3r/hatch3r · 28 tokens

hatch3r-migration-plan

Create a phased migration plan for a major dependency or framework upgrade. Analyzes breaking changes and produces an actionable plan with rollback procedures.

hatch3r/hatch3r · 27 tokens

hatch3r-onboard

Generate a comprehensive onboarding guide for a new developer joining the project -- spawn parallel researchers to analyze codebase structure, architecture, and conventions, then produce a tailored onboarding document with setup instructions, architecture walkthrough, coding conventions, key workflows, tribal…

hatch3r/hatch3r · 56 tokens

csm-goals

List, set, or update tracked goals for this project.

NovasPlace/CSM · 12 tokens

feature

Create a new feature via SDLC-based multi-agent collaboration.

sawrus/agent-guides · 11 tokens