Borrowing it
Nothing to install: this file belongs to stolostron/jira-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/stolostron/jira-mcp-server/main/.claude/commands/jira-create.mdgit clone --depth 1 https://github.com/stolostron/jira-mcp-serverWrote 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/stolostron/jira-mcp-server/jira-create)<a href="https://agentmods.dev/commands/stolostron/jira-mcp-server/jira-create"><img src="https://agentmods.dev/badge/commands/stolostron/jira-mcp-server/jira-create/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/stolostron/jira-mcp-server/jira-create"><img src="https://agentmods.dev/badge/commands/stolostron/jira-mcp-server/jira-create.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.00000 | $0.01105 |
| Opus 5 | $0.00000 | $0.00553 |
| Sonnet 5 | $0.00000 | $0.00221 |
| Haiku 4.5 | $0.00000 | $0.00111 |
Grade A, and why
jira-create 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 8d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Create Command
Create a new Jira issue interactively using AskUserQuestion to collect all required and optional fields.
Instructions
Follow these steps in order. Use AskUserQuestion for each step. Do NOT skip steps or guess values.
Step 1: Issue Type
Use AskUserQuestion to ask the user what type of issue to create:
- Story — User-facing functionality with acceptance criteria
- Bug — Defect report with reproduction steps
- Task — Internal technical work, non-user-facing
- Spike — Research, investigation, or proof-of-concept
- Feature — Significant customer-facing capability
- Epic — Large body of work spanning multiple sprints
- Sub-task — Child task under an existing issue
Step 2: Delegate to Specialist Agent
Based on the issue type selected, launch the appropriate specialist agent to help craft the content. The agent should help formulate the summary, description, and any type-specific fields:
| Issue Type | Agent | Purpose |
|---|---|---|
| Story | story-specialist |
Craft user story format, acceptance criteria, definition of done |
| Bug | bug-specialist |
Structure reproduction steps, expected vs actual behavior, severity |
| Task | task-specialist |
Technical breakdown, implementation details |
| Spike | spike-specialist |
Research questions, success criteria, time-box |
| Feature | feature-specialist |
Feature strategy, user impact, rollout plan |
| Epic | epic-specialist |
Epic scope, child story breakdown, cross-team coordination |
| Sub-task | task-specialist |
Scoped sub-task breakdown |
The agent should return a proposed summary and description. Present them to the user for approval or editing via AskUserQuestion.
Step 3: Collect Core Fields
Use AskUserQuestion to collect the remaining fields. Group questions logically (up to 4 questions per call). You may batch related fields together.
Priority (default: Normal):
- Blocker
- Critical
- Major
- Normal (Recommended)
- Minor
- Trivial
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.
- 8d ago First seen · 124 lines · 0 tokens per session scan A 23e41300d75a
jira-create is a command published in the GitHub repository stolostron/jira-mcp-server (2 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,105 tokens. 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
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.