A JIRA ticket manager for creating, viewing, editing, assigning, moving through workflow, versioning, and copying issues. JIRA is a system teams use to track bugs, tasks, and planned work.

Create and update bugs, stories, tasks, and epics; assign them; change their workflow status; manage versions; and clone existing tickets.

It removes the need to remember separate commands or open JIRA for common issue updates. It also asks for missing details when creating a ticket.

ticket — Skill for Claude Code by quay

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 quay/ai-helpers --skill ticket

Clone the repo

git clone --depth 1 https://github.com/quay/ai-helpers

Made for: Claude Code.

Or install jira, the plugin that ships this one along with the rest of its 2 skills, 6 commands.

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/quay/ai-helpers/ticket.svg)](https://agentmods.dev/skills/quay/ai-helpers/ticket)

Your own site

<a href="https://agentmods.dev/skills/quay/ai-helpers/ticket"><img src="https://agentmods.dev/badge/skills/quay/ai-helpers/ticket.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 1,482 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 2 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.00038	$0.01482
Opus 5	$0.00019	$0.00741
Sonnet 5	$0.00008	$0.00296
Haiku 4.5	$0.00004	$0.00148

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

Security

Grade B, and why

ticket scanned grade B with 2 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 2d 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

curl -sS -u "$EMAIL:$TOKEN" -X PUT -H "Content-Type: application/json" -d @- \

Makes network callslowCapability

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

- Bash(curl -sS -u * https://*.atlassian.net/rest/api/3/*)

plugins/jira/skills/ticket/SKILL.md · 158 lines

How it starts

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

JIRA Ticket Operations

Parse $ARGUMENTS to determine the action:

Starts with create → Create a new ticket
Contains an issue key (e.g., PROJQUAY-1234) → View by default, or the specified action
Actions: view, create, edit, assign, transition, check-version, set-version, clone

JIRA API Access

Use the acli CLI for all operations. For custom field writes (set-version, components, priority on existing issues), fall back to REST API with curl.

REST credentials: ~/.config/acli/jira_config.yaml (email), ~/.config/acli/token.txt or $JIRA_API_TOKEN (token).

Target Version field: ${JIRA_TARGET_VERSION_FIELD:-customfield_10855}. Domain: ${JIRA_DOMAIN:-redhat.atlassian.net}.

Operations

Create

Gather required fields interactively — ask the user for anything not provided in $ARGUMENTS:

Project (required): PROJQUAY or QUAYIO
Type (required): Bug, Story, Task, or Epic
Summary (required): concise title, under 100 characters
Description (required): expand the user's input with clarifying questions (current vs expected behavior, steps to reproduce, acceptance criteria)
Component: quay, quay-ui, quay-operator (PROJQUAY) or quay.io (QUAYIO)
Priority: Critical, Major, Minor, or Undefined (default)
Assignee: defaults to @me
Labels: suggest eus-applicable for CVE/security fixes

Present a summary for confirmation before creating.

acli jira workitem create \
  --project "$PROJECT" --type "$TYPE" --summary "$SUMMARY" \
  --description "$DESCRIPTION" --assignee "${ASSIGNEE:-@me}" \
  --label "$LABELS" --json

For fields acli create does not support natively (components, priority, epic link), set them via REST after creation:

curl -sS -u "$EMAIL:$TOKEN" -X PUT -H "Content-Type: application/json" \
  -d '{"fields":{"components":[{"name":"COMPONENT"}],"priority":{"name":"PRIORITY"}}}' \
  "https://${JIRA_DOMAIN:-redhat.atlassian.net}/rest/api/3/issue/$ISSUE_KEY"

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

2d ago First seen · 158 lines · 38 tokens per session scan B 15e50e8c39b3

Subscribe to this mod's changes

ticket is a skill published in the GitHub repository quay/ai-helpers (3 stars, last pushed 19d ago), licensed MIT. It adds 38 tokens to every session and 1,482 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Project management

recipe-create-meet-space

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

googleworkspace/cli · 18 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

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

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

ticket