A command that drafts a GitHub issue from sprint research, specifications, or an execution wave. A GitHub issue is a tracked work item for a software project.

Use it to draft research, specification, or wave issues for backend, library, frontend, integration, or infrastructure work, then optionally push them to GitHub.

It turns internal planning documents into a consistent issue draft while keeping the supporting evidence attached. Creating the issue remotely remains an explicit choice.

issue — Command by koolamusic

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/koolamusic/claudefiles/issue

Clone the repo

git clone --depth 1 https://github.com/koolamusic/claudefiles

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

When invoked 1,899 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.

Model	Per session	Once invoked
Fable 5	$0.00041	$0.01899
Opus 5	$0.00020	$0.00949
Sonnet 5	$0.00008	$0.00380
Haiku 4.5	$0.00004	$0.00190

Measured 2d ago against content hash b1dff4b387a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

issue 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 2d 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.

plugins/jira/commands/issue.md · 139 lines

How it starts

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

Draft a GitHub issue from internal sprint artifacts. The shape decides the template; the domain decides the evidence layer. Default behavior saves a draft to disk; pushing is explicit.

Parse the input

$ARGUMENTS must include:

Shape (positional, required): research | spec | wave
--domain <name> (required): backend | library | frontend | integration | infra
--wave <roman> (required for wave shape): the wave identifier, e.g. --wave II
--push (optional): actually create the GitHub issue after drafting
--sprint <slug> (optional): override the active sprint

If shape or domain is missing, use AskUserQuestion to collect them (bundle into one question). Do not guess.

Steps

Locate the sprint.
- If --sprint <slug> provided, use it.
- Otherwise slug=$(cat .jira/CURRENT). If empty or missing, stop — there is no active sprint to draw from. Tell the user to run /jira:research or pass --sprint.
Verify source docs by shape:
- research — requires .jira/sprints/<slug>/RESEARCH.md
- spec — requires at least one .jira/sprints/<slug>/*-PLAN.md and .jira/sprints/<slug>/CONTEXT.md
- wave — requires the specific .jira/sprints/<slug>/<NN>-PLAN.md matching --wave <roman>. Map Roman to the NN prefix by reading the wave: field in each PLAN's frontmatter. If ambiguous (two plans in the same wave), list them via AskUserQuestion and ask which one.
If a required source is missing, stop and tell the user what to do (/jira:research → /jira:plan → then /jira:issue).
Read the guide and template.
- Always read ${CLAUDE_PLUGIN_ROOT}/templates/issue/GUIDE.md first — it defines the principles and the domain matrix.
- Read ${CLAUDE_PLUGIN_ROOT}/templates/author-conventions.md too — the public/internal boundary for the body: no internal decision IDs, .jira/ paths, or jargon; locked decisions become constraints or acceptance criteria.
- Then read ${CLAUDE_PLUGIN_ROOT}/templates/issue/<shape>.md.

Read the full file on GitHub · 139 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.

2d ago First seen · 139 lines · 41 tokens per session scan A b1dff4b387a2

Subscribe to this mod's changes

issue is a command published in the GitHub repository koolamusic/claudefiles (132 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 1,899 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.

Project management

issue

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Parse the input

Steps

What this file has done since we first saw it

Other commands, from other repositories

template

project-recap

speckit.taskstoissues

ado-pull

issue-amend

dispatch-worker