create-ticket

A command that analyses a codebase and creates a detailed Jira ticket, a structured task record for software work.

In plain words
What is it for?
Use it to prepare Jira tickets for features or fixes that another command, such as /implement-feature, can execute.
Why use it?
It turns code findings into implementation-ready work items, reducing the effort needed to describe a change clearly.

Command

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 commands/wonjun3991/study/create-ticket
Clone the repo
git clone --depth 1 https://github.com/wonjun3991/study
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 2,871 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin unknown 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 $0.00019 $0.02871
Opus 5 $0.00010 $0.01435
Sonnet 5 $0.00004 $0.00574
Haiku 4.5 $0.00002 $0.00287

Measured yesterday against content hash 80270c17e287, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-ticket scanned grade A with 1 finding 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 yesterday.

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.

Makes network callslowCapability

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

6. **Creates Jira ticket** - Using Jira REST API (curl) with all the details
presentation/harness-engineering/reference/commands/create-ticket.md · 379 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. yesterday First seen · 379 lines · 19 tokens per session scan A 80270c17e287

Subscribe to this mod's changes

create-ticket is a command published in the GitHub repository wonjun3991/study (2 stars, last pushed 3mo ago), with no licence file. It adds 19 tokens to every session and 2,871 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.