Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add koolamusic/claudefiles/plugin install jiraWrote 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.
[](https://agentmods.dev/commands/koolamusic/claudefiles/issue)<a href="https://agentmods.dev/commands/koolamusic/claudefiles/issue"><img src="https://agentmods.dev/badge/commands/koolamusic/claudefiles/issue/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.
<a href="https://agentmods.dev/commands/koolamusic/claudefiles/issue"><img src="https://agentmods.dev/badge/commands/koolamusic/claudefiles/issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00041 | $0.01899 |
| Opus 5.5 | $0.00016 | $0.00760 |
| Sonnet 5.5 | $0.00008 | $0.00380 |
| Haiku 4.5 | $0.00004 | $0.00190 |
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 1mo 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.
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 forwaveshape): 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:researchor pass--sprint.
- If
-
Verify source docs by shape:
research— requires.jira/sprints/<slug>/RESEARCH.mdspec— requires at least one.jira/sprints/<slug>/*-PLAN.mdand.jira/sprints/<slug>/CONTEXT.mdwave— requires the specific.jira/sprints/<slug>/<NN>-PLAN.mdmatching--wave <roman>. Map Roman to the NN prefix by reading thewave:field in each PLAN's frontmatter. If ambiguous (two plans in the same wave), list them viaAskUserQuestionand 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.mdfirst — it defines the principles and the domain matrix. - Read
${CLAUDE_PLUGIN_ROOT}/templates/author-conventions.mdtoo — 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.
- Always read
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.
- 1mo ago First seen · 139 lines · 41 tokens per session scan A b1dff4b387a2
issue is a command published in the GitHub repository koolamusic/claudefiles (130 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 1,899 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.