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-authoringgit 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-authoring)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-jira-authoring"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-jira-authoring/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-authoring"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-jira-authoring.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.00169 | $0.01064 |
| Opus 5 | $0.00084 | $0.00532 |
| Sonnet 5 | $0.00034 | $0.00213 |
| Haiku 4.5 | $0.00017 | $0.00106 |
Grade A, and why
rhdh-jira-authoring 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 12d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH Jira authoring
The material that decides whether an issue is worth reading six months later.
Two skills use it — /rhdh-jira-create while drafting and /rhdh-jira-refine
while auditing — so it lives here rather than in either of them.
This skill produces text and judgements. It never runs a Jira command and never performs a write.
Route by need
| Need | Load |
|---|---|
| How to challenge a draft; how to infer RHDH Jira fields from conversation | references/grill.md |
| T-shirt sizes, story points, RHDHSUPP effort points, sizing challenges | references/sizing.md |
| Does this already exist? | references/duplicates.md |
| Splitting a Feature into Epics or an Epic into Stories | references/work-breakdown.md |
Templates and examples
Description templates are Jira wiki markup. Each has a filled example next to it for tone and detail calibration — read the example before drafting, because the templates alone underspecify how much detail an RHDH reviewer expects.
| Issue type | Usual project | Template | Example |
|---|---|---|---|
| Feature | RHDHPLAN | assets/templates/feature.txt |
assets/examples/feature-example.txt |
| Epic | RHIDP | assets/templates/epic.txt |
assets/examples/epic-example.txt |
| Story | RHIDP | assets/templates/story.txt |
assets/examples/story-example.txt |
| Task | RHIDP | assets/templates/task.txt |
assets/examples/task-example.txt |
| Bug | RHDHBUGS | assets/templates/bug.txt |
assets/examples/bug-example.txt |
Spikes use the Task template with a SPIKE: prefix on the summary and a
time-boxed story point estimate. A Vulnerability uses the Story template and
always carries the Security component. Feature Request and Outcome templates
exist in RHDHPLAN; this skill does not carry them, so draft those from the
project's own template in the Jira UI.
Sub-tasks are children of an existing issue, never standalone.
What ships with it
15 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.
- agents/openai.yaml 129 B
- assets/examples/bug-example.txt 1.4 KB
- assets/examples/epic-example.txt 2.4 KB
- assets/examples/feature-example.txt 2.1 KB
- assets/examples/story-example.txt 2.1 KB
- assets/examples/task-example.txt 1004 B
- assets/templates/bug.txt 314 B
- assets/templates/epic.txt 1.0 KB
- assets/templates/feature.txt 1.6 KB
- assets/templates/story.txt 1.5 KB
- assets/templates/task.txt 239 B
- references/duplicates.md 2.0 KB
- references/grill.md 15 KB
- references/sizing.md 4.3 KB
- references/work-breakdown.md 3.3 KB
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.
- 12d ago First seen · 85 lines · 169 tokens per session scan A 0bb31d50ae9f
rhdh-jira-authoring is a skill published in the GitHub repository redhat-developer/rhdh-skills (17 stars, last pushed 3d ago), licensed Apache-2.0. It adds 169 tokens to every session and 1,064 once invoked, about $0.0008 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.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.