open-supply-hub: Command for Claude Code

.claude/commands/jira-ticket.md

jira-ticket is a command for Claude Code from opensupplyhub/open-supply-hub. It costs 49 tokens per session (135 once invoked), scanned A, original, MIT.

A command for drafting, reviewing, and filing Jira stories or epics in Open Supply Hub's required format. Jira stories describe user needs, while epics group larger bodies of work.

In plain words
What is it for?
Use it to prepare OS Hub Jira tickets, review their wording, and collect fields such as parent, priority, labels, and other filing details.
Why use it?
It helps turn requirements into a consistent ticket with explicit requirements and Given-When-Then acceptance criteria before it is filed.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

This is opensupplyhub/open-supply-hub's own configuration. It tells Claude Code how to work on open-supply-hub itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything open-supply-hub configures →

Reuse

Borrowing it

Nothing to install: this file belongs to opensupplyhub/open-supply-hub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/opensupplyhub/open-supply-hub/main/.claude/commands/jira-ticket.md
Clone the repo
git clone --depth 1 https://github.com/opensupplyhub/open-supply-hub

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 jira-ticket

README.md
[![agentmods](https://agentmods.dev/badge/commands/opensupplyhub/open-supply-hub/jira-ticket/github.svg)](https://agentmods.dev/commands/opensupplyhub/open-supply-hub/jira-ticket)
Your own site
<a href="https://agentmods.dev/commands/opensupplyhub/open-supply-hub/jira-ticket"><img src="https://agentmods.dev/badge/commands/opensupplyhub/open-supply-hub/jira-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 jira-ticket

Your own site · 80×15
<a href="https://agentmods.dev/commands/opensupplyhub/open-supply-hub/jira-ticket"><img src="https://agentmods.dev/badge/commands/opensupplyhub/open-supply-hub/jira-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 135 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.00049 $0.00135
Opus 5 $0.00024 $0.00068
Sonnet 5 $0.00010 $0.00027
Haiku 4.5 $0.00005 $0.00014

Measured 11d ago against content hash 72b5a3a69bec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

jira-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 11d 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/jira-ticket.md · 9 lines

What it actually says

Invoke the jira-ticket-writer skill with arguments: $ARGUMENTS

The skill is the source of truth. This command is a thin wrapper for explicit invocation.

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. 11d ago First seen · 9 lines · 49 tokens per session scan A 72b5a3a69bec

Subscribe to this mod's changes

jira-ticket is a command published in the GitHub repository opensupplyhub/open-supply-hub (20 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 135 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-30.