start-ticket

start-ticket is a skill for Claude Code from flurdy/agent-skills. It costs 33 tokens per session (1,014 once invoked), scanned A, original, MIT.

A workflow for starting work on a Jira ticket. Jira is a system for tracking software tasks, bugs, and other work items; the workflow creates a matching Git branch.

In plain words
What is it for?
Fetching a Jira ticket, selecting a prefix such as feature, fix, or documentation, and creating a concise branch name from the ticket summary.
Why use it?
It avoids manually looking up the ticket, choosing a branch prefix, and formatting the branch name. The branch then reflects both the kind of work and the ticket number.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; names the AskUserQuestion tool.

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 skills/flurdy/agent-skills/start-ticket
Any agent
npx skills add flurdy/agent-skills --skill start-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.

agentmods badge for start-ticket

README.md
[![agentmods](https://agentmods.dev/badge/skills/flurdy/agent-skills/start-ticket.svg)](https://agentmods.dev/skills/flurdy/agent-skills/start-ticket)
Your own site
<a href="https://agentmods.dev/skills/flurdy/agent-skills/start-ticket"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/start-ticket.svg" alt="Measured on agentmods" 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 1,014 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.1 $0.00033 $0.01014
Opus 5 $0.00016 $0.00507
Sonnet 5 $0.00007 $0.00203
Haiku 4.5 $0.00003 $0.00101

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

Security

Grade A, and why

start-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 6d 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/start-ticket/SKILL.md · 105 lines

How it starts

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

Start Ticket

Initialize work on a Jira ticket by looking up the ticket details and creating an appropriately named branch.

Usage

/start-ticket AB-123

Instructions

1. Look Up the Jira Ticket

Use the /jira-ticket skill or the Jira MCP tools directly 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}"

2. Determine the 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. Generate Branch Name

Format: {prefix}/{TICKET-NUMBER}-{kebab-case-summary}

Rules:

  • Convert summary to kebab-case (lowercase, hyphens instead of spaces)
  • Remove special characters except hyphens
  • Truncate to reasonable length (max ~50 chars for the summary portion)
  • Keep the ticket number uppercase

Example: For ticket AB-123 with summary "Sanitize Input":

feat/AB-123-sanitize-input

3b. Resume awareness — check for a prior handoff

Before creating a fresh branch, check whether a previous session already worked this ticket and left a /wrap-up handoff. "Start ticket" is the new-work entry point, but the same ticket sometimes comes back — and a handoff means there's likely an existing branch plus open threads you'd otherwise re-create from scratch.

Two-step so the usual case (a genuinely new ticket) stays network-free:

  1. Cheap pass (no network):
    ~/.agents/skills/handoffs/scripts/list.sh --ticket {TICKET-NUMBER}
    
    Read ---MATCHED-HANDOFFS--- (current-repo, supersede-filtered, newest first). Empty → skip to step 4 and create the branch normally. This is the usual path.
  2. Confirm live (only if step 1 matched):
    ~/.agents/skills/handoffs/scripts/list.sh --check-branches --ticket {TICKET-NUMBER}
    
    Still empty → the earlier work shipped; create a fresh branch (step 4). Otherwise take the newest matched line: {filename}|{date}|{time}|{slug}|{branch}|{exists}|{pr-state}|{pr-number}|{pr-url}.

Read the full file on GitHub · 105 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. 6d ago First seen · 105 lines · 33 tokens per session scan A 92b1fe6eda57

Subscribe to this mod's changes

start-ticket is a skill published in the GitHub repository flurdy/agent-skills (8 stars, last pushed 8d ago), licensed MIT. It adds 33 tokens to every session and 1,014 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.