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.
npx skills add redhat-developer/rhdh-skills --skill rhdh-jira-creategit clone --depth 1 https://github.com/redhat-developer/rhdh-skillsWrote 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/skills/redhat-developer/rhdh-skills/rhdh-jira-create)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-jira-create"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-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/skills/redhat-developer/rhdh-skills/rhdh-jira-create"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-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.00184 | $0.00909 |
| Opus 5 | $0.00092 | $0.00454 |
| Sonnet 5 | $0.00037 | $0.00182 |
| Haiku 4.5 | $0.00018 | $0.00091 |
Grade A, and why
rhdh-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 9d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create RHDH Jira work
One skill for "this should be a ticket". It decides the issue type and project, runs the interview, drafts from the RHDH template, and creates the issue.
A caller who says "file this in Jira" almost never knows whether they want a Feature, an Epic, or a Story. Deciding that is this skill's job. Getting it wrong writes the wrong issue type into a public project, so the decision happens up front and out loud, and the user confirms it before anything is created.
Route
Load workflows/create-issue.md. One workflow covers every level of the
hierarchy — the type decision is its first real step, and the steps after it
converge.
Add references/support-intake.md when the work originates from a support case:
an RHDHSUPP conversation, a customer escalation, an SLA question, or a request to
turn a case into a defect or a feature request.
Grilling is a hard gate
Creation requires the external grilling skill. It is not bundled with this
pack. If the host cannot invoke it by name, stop before creating anything, say
that creation is gated on grilling, and name /setup-rhdh-skills install.
Never probe host skill directories, install it yourself, or improvise a
substitute interview.
/rhdh-jira-authoring carries the RHDH half of the interview — the challenge
matrix, field inference, sizing, and templates. Invoke it by name.
Every create is an external write
Invoke /mutation-gate and follow it before any acli command that
creates, links, comments, or edits. One create is rarely one operation — the
create, the field update create could not carry, the parent link, and the
comment go into the same stated set so a single approval covers them.
Afterwards, read the issue back. A create that succeeded followed by a field update that silently failed is a half-created issue, not a success.
Boundary with the neighbouring skills
- Judging whether an existing issue is ready is
/rhdh-jira-refine. - Changing status, assignee, comments, or links on a known key is
/rhdh-jira-update. aclisyntax, field IDs, the component catalog, and workflow exit criteria are/rhdh-jira-api.- Templates, the challenge matrix, sizing, duplicate detection, and decomposition
rules are
/rhdh-jira-authoring. - Creating a PR and linking it back to an issue is
/rhdh-jira-link.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 76 lines · 184 tokens per session scan A 4e92385b1677
rhdh-jira-create is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed today), licensed Apache-2.0. It adds 184 tokens to every session and 909 once invoked, about $0.0009 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.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.