A command that takes a Jira ticket, moves it to “In Progress,” creates a Git branch for it, and checks out that branch locally.

Use it when starting work on a Jira task. Give it the ticket key so it can fetch the issue, update its status, create a branch from main, and switch your local repository to it.

It removes the repeated setup work between choosing a ticket and starting its code changes. The Jira issue and local branch are linked from the beginning.

ticket — Command for Claude Code by runnithan/claudex-setup

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/runnithan/claudex-setup

Made for: Claude Code.

Or install claudex-setup, the plugin that ships this one along with the rest of its 3 skills, 24 commands, 6 agents, 1 hook.

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/runnithan/claudex-setup/ticket/github.svg)](https://agentmods.dev/commands/runnithan/claudex-setup/ticket)

Your own site

<a href="https://agentmods.dev/commands/runnithan/claudex-setup/ticket"><img src="https://agentmods.dev/badge/commands/runnithan/claudex-setup/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/commands/runnithan/claudex-setup/ticket"><img src="https://agentmods.dev/badge/commands/runnithan/claudex-setup/ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 259 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.00019	$0.00259
Opus 5.5	$0.00008	$0.00104
Sonnet 5.5	$0.00004	$0.00052
Haiku 4.5	$0.00002	$0.00026

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

Security

Grade A, and why

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 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.

.claude/commands/ticket.md · 18 lines

What it actually says

Pick up the Jira ticket $ARGUMENTS and set up for development:

Fetch the ticket using mcp__atlassian__getJiraIssue with key $ARGUMENTS. Display the summary, description, type, and current status.
Transition to In Progress: Call mcp__atlassian__getTransitionsForJiraIssue to get available transitions, then mcp__atlassian__transitionJiraIssue to move it to "In Progress".
Create a feature branch: Generate a branch name as {ticket-key}-{slugified-summary} (lowercase, hyphens, max 50 chars). Create it from main using mcp__github__create_branch with owner YOUR_ORG, repo YOUR_REPO.
Checkout locally: Run git fetch origin && git checkout {branch-name}.
Report: Confirm the ticket is in progress, the branch exists, and you're checked out on it.

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 First seen · 18 lines · 19 tokens per session scan A f7fd7468de20

Subscribe to this mod's changes

ticket is a command published in the GitHub repository runnithan/claudex-setup (1 stars, last pushed 7d ago), licensed MIT. It adds 19 tokens to every session and 259 once invoked, about $0.0001 per session on Opus 5.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.

Claude Code Git and workflow Project management agents ai anthropic claude claude-code-plugin

ticket

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

update-check.template

create-task-list-for-issue.template

update-smart.template

sync-coordinator

github-modes

pull-repos