work-on-ticket

work-on-ticket is a skill for Claude Code, Codex from jjmartres/ai-coding-agents. It costs 41 tokens per session (2,290 once invoked), scanned A, original, MIT.

A workflow for starting work on a Jira ticket, a tracked software-development task. It retrieves the ticket, creates a suitably named branch, and begins planning.

In plain words
What is it for?
Use it when asked to start or pick up a ticket such as AGP-123, including fetching its summary, description, type, priority, and status.
Why use it?
It avoids manually copying ticket details, choosing a branch name, and setting up the initial work process.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions OpenCode.

Good fit Use it when asked to start or pick up a ticket such as AGP-123, including fetching its summary, description, type, priority, and status.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jjmartres/ai-coding-agents/work-on-ticket
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 jjmartres/ai-coding-agents --skill work-on-ticket
Clone the repo
git clone --depth 1 https://github.com/jjmartres/ai-coding-agents

Made for: Claude Code, Codex.

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 work-on-ticket

README.md
[![agentmods](https://agentmods.dev/badge/skills/jjmartres/ai-coding-agents/work-on-ticket/github.svg)](https://agentmods.dev/skills/jjmartres/ai-coding-agents/work-on-ticket)
Your own site
<a href="https://agentmods.dev/skills/jjmartres/ai-coding-agents/work-on-ticket"><img src="https://agentmods.dev/badge/skills/jjmartres/ai-coding-agents/work-on-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.

agentmods 80×15 button for work-on-ticket

Your own site · 80×15
<a href="https://agentmods.dev/skills/jjmartres/ai-coding-agents/work-on-ticket"><img src="https://agentmods.dev/badge/skills/jjmartres/ai-coding-agents/work-on-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,290 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.02290
Opus 5.5 $0.00016 $0.00916
Sonnet 5.5 $0.00008 $0.00458
Haiku 4.5 $0.00004 $0.00229

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

Security

Grade A, and why

work-on-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 26d 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.

shared/.ai-agents/skills/work-on-ticket/SKILL.md · 334 lines

How it starts

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

Work on Ticket

Streamlined workflow to start work on a Jira ticket by fetching ticket details, creating a branch, and initiating task planning.

When to Use This Skill

Activate this skill when:

  • The user says "work on AGP-123" or "start work on AGP-123"
  • The user says "pick up AGP-123" or "begin AGP-123"
  • The user mentions starting work on a specific Jira ticket ID
  • Pattern: work on [TICKET_ID] or similar intent

Workflow

1. Parse Ticket ID

Extract the Jira ticket ID from the user's message. Common patterns:

  • work on AGP-782
  • start AGP-782
  • pick up PROJ-123

Ticket ID format: [A-Z]+-[0-9]+ (e.g., AGP-782, AICC-123)

2. Fetch Jira Ticket Details

Use the MCP Zapier tool to fetch the ticket:

mcp__zapier -
  frontend__jira_software_cloud_find_issue_by_key({
    instructions: "Get details for ticket [TICKET_ID]",
    key: "[TICKET_ID]",
    fields: "summary,description,issuetype,priority,status",
  });

Extract from response:

  • Summary (title)
  • Description
  • Issue type
  • Status
  • Any other relevant context

3. Generate Branch Name

Create a branch name using this format:

[TICKET_ID]-[kebab-case-summary]

Branch Naming Rules:

  • Start with the ticket ID (e.g., AGP-782-)
  • Convert summary to kebab-case (lowercase, dashes instead of spaces)
  • Remove special characters
  • Keep it concise (max 50 characters total)
  • Use meaningful words from the summary

Examples:

  • AGP-782-migrate-existing-mcp-server
  • AICC-123-fix-auth-token-expiry
  • PROJ-456-add-user-settings-page

Implementation:

# Convert summary to kebab-case
# Example: "Migrate existing MCP server" -> "migrate-existing-mcp-server"

4. Create Isolated Worktree under .worktree/

In accordance with the Git Worktree Policy, do NOT run git checkout -b in the primary workspace. Create an isolated worktree under .worktree/:

BRANCH_NAME="[TICKET_ID]-[kebab-case-summary]"
REPO_ROOT=$(git rev-parse --show-toplevel)

# Ensure .worktree/ is ignored
grep -q "^\.worktree/" .gitignore 2>/dev/null || echo ".worktree/" >> .gitignore

# Fetch latest default branch
git fetch origin

# Create isolated worktree under .worktree/
git worktree add ".worktree/${BRANCH_NAME}" -b "${BRANCH_NAME}"

Read the full file on GitHub · 334 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. 26d ago Changed · -11 lines b466cdc85972
  2. 1mo ago First seen · 345 lines · 41 tokens per session scan A 8bd3cb3cae26

Subscribe to this mod's changes

work-on-ticket is a skill published in the GitHub repository jjmartres/ai-coding-agents (48 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 2,290 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

pod-init

Initialize CocoPlus project bundle in the current directory. Creates .cocoplus/ directory structure, copies all templates, initializes AGENTS.md, project.md, flow.json, and creates the initial git commit. Run this once per project before using any other CocoPlus command.

Snowflake-Labs/cocoplus · 57 tokens

cocoplus-config

CocoPlus configuration SSOT — $cocoplus sync propagates cocoplus.toml into downstream artifacts; $cocoplus migrate-config converts legacy safety-config.json. Invoked via $cocoplus sync and $cocoplus migrate-config.

Snowflake-Labs/cocoplus · 56 tokens

audit-pr

Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".

gtrabanco/agentic-workflow · 71 tokens

execute-phase

Step executor for units whose triage (unit-lane) decided which steps the unit needs. Implements one triaged step (or all remaining steps), with frozen acceptance, step-local gates, commits, red-gate repair, and diff-size guard. BREAKING: replaced PLAN.md/TASKS.md/progress.md/ACCEPTANCE.md with the unit doc's Tasks…

gtrabanco/agentic-workflow · 106 tokens

unit-lane

One-shot lane conductor for a delivery unit: triage, implement, evidence, and close in a single document. Triggers: "unit-lane", "run the lane", "work on this feature/fix", "build this unit".

gtrabanco/agentic-workflow · 53 tokens

workflow-status

Read-only workflow sensor: run the deterministic script, read the fixed machine envelope, interpret the recommendation. Never edits. Triggers: "workflow-status", "workflow status", "what can I build next".

gtrabanco/agentic-workflow · 44 tokens