create-issue

A command for creating a Jira issue, a trackable work item in Jira, from structured details or Markdown text. It can include a summary, issue type, description, labels, user story, acceptance criteria, and definition of done.

In plain words
What is it for?
Use it to create bugs, stories, and other Jira issues with clear descriptions, labels, user stories, acceptance checks, and completion requirements.
Why use it?
It reduces the manual work of opening Jira and reformatting a request. Markdown can be converted into Jira's supported formatting.

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/dmzoneill/redhat-ai-workflow/create-issue
Clone the repo
git clone --depth 1 https://github.com/dmzoneill/redhat-ai-workflow
Per session 0 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,464 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01464
Opus 5 $0.00000 $0.00732
Sonnet 5 $0.00000 $0.00293
Haiku 4.5 $0.00000 $0.00146

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

Security

Grade A, and why

create-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.

docs/commands/create-issue.md · 192 lines

How it starts

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

/create-issue

Description: Create a Jira issue with Markdown support and auto-conversion.

Overview

Description: Create a Jira issue with Markdown support and auto-conversion.

Underlying Skill: create_jira_issue

This command is a wrapper that calls the create_jira_issue skill. For detailed process information, see skills/create_jira_issue.md.

Arguments

Argument Required Description
summary No -
issue_type No -
description No -
labels No -

Usage

Examples

skill_run("create_jira_issue", '{
  "summary": "Add pytest-xdist parallelization",
  "issue_type": "story",
  "description": "## Overview\n\nSpeed up test suite with parallel execution.",
  "labels": ["testing", "performance"]
}')
skill_run("create_jira_issue", '{
  "summary": "Add pytest-xdist parallelization",
  "issue_type": "story",
  "description": "Speed up test suite with parallel execution",
  "user_story": "As a developer, I want tests to run in parallel so that CI is faster.",
  "acceptance_criteria": "- [ ] Tests run in parallel\\n- [ ] No flaky tests\\n- [ ] 50% faster",
  "definition_of_done": "- Tests pass\\n- Code reviewed\\n- Documentation updated",
  "labels": ["testing", "performance"],
  "components": ["Automation Analytics"],
  "story_points": 5,
  "epic_link": "AAP-12000"
}')
skill_run("create_jira_issue", '{
  "summary": "API returns 500 on empty request",
  "issue_type": "bug",
  "description": "## Steps to Reproduce\\n\\n1. Send empty POST\\n2. See error"
}')

Process Flow

This command invokes the create_jira_issue skill. The process flow is:

flowchart LR
    START([User runs /create-issue]) --> VALIDATE[Validate Arguments]
    VALIDATE --> CALL[Call create_jira_issue skill]
    CALL --> EXECUTE[Execute Skill Steps]
    EXECUTE --> RESULT[Return Result]
    RESULT --> END([Complete])

    style START fill:#6366f1,stroke:#4f46e5,color:#fff
    style END fill:#10b981,stroke:#059669,color:#fff
    style CALL fill:#3b82f6,stroke:#2563eb,color:#fff
```bash

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

  1. 2d ago First seen · 192 lines · 0 tokens per session scan A 35368964a210

Subscribe to this mod's changes

create-issue is a command published in the GitHub repository dmzoneill/redhat-ai-workflow (5 stars, last pushed 23d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,464 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.