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-updategit 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-update)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-jira-update"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-jira-update/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-update"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-jira-update.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.00158 | $0.00775 |
| Opus 5 | $0.00079 | $0.00387 |
| Sonnet 5 | $0.00032 | $0.00155 |
| Haiku 4.5 | $0.00016 | $0.00077 |
Grade A, and why
rhdh-jira-update 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 10d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update RHDH Jira work
Small, precise changes to an issue that already exists. Two jobs live here because they are the same job: a field mutation on a known key.
Route
| Intent | Load |
|---|---|
| Log progress, transition status, link a PR, close something out | workflows/update-issue.md |
| Decide who should take the work, then assign it | workflows/assign-work.md |
Both may run in one session — an update that ends "and hand this to someone" is the second workflow, not a new conversation.
Every change is an external write
Invoke /mutation-gate and follow it, then read back the fields you claimed
to set.
When another skill hands over a caller-finalized comment body and reports
that the user approved that exact body through /mutation-gate, use those bytes
for the write only when the current transcript contains that operation's plan
and approval. Do not compose, edit, present, or confirm the body again. A label
or an assertion of earlier approval is not proof; without the plan and approval
in this transcript, run the gate before writing.
A caller handing over a pull request usually wants three writes at once — a
comment, a transition to Review, and a web link to the PR URL. Put all three in
one stated set so one approval covers them, rather than asking three times.
Boundary with the neighbouring skills
- Opening new work is
/rhdh-jira-create. - Auditing many issues for readiness is
/rhdh-jira-refine. This skill changes one issue you already named. - Sprint carryover, velocity, and fill suggestions are
/rhdh-jira-sprint-plan; it invokes this skill for per-issue assignee recommendations rather than scoring them itself. acliflags, field IDs, JQL, GraphQL roster queries, and workflow exit criteria are/rhdh-jira-api.- Creating a PR and attaching the Jira web link in one step is
/rhdh-jira-link.
Completion
Complete when every issue key the answer mentions was read back after the change and reported with its resulting status, assignee, and links. Name every operation that ran and every one that failed — a comment that posted followed by a transition that was rejected is a partial update, not a success. A transition blocked by unmet exit criteria is reported with the specific fields that blocked it. An assignee recommendation names the evidence behind it and says plainly when component or sprint metadata was missing, rather than implying certainty it does not have.
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.
- 10d ago First seen · 69 lines · 158 tokens per session scan A ccf1522cf20b
rhdh-jira-update is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed yesterday), licensed Apache-2.0. It adds 158 tokens to every session and 775 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.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.