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-apigit 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-api)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-jira-api"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-jira-api/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-api"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-jira-api.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.00166 | $0.01272 |
| Opus 5 | $0.00083 | $0.00636 |
| Sonnet 5 | $0.00033 | $0.00254 |
| Haiku 4.5 | $0.00017 | $0.00127 |
Grade A, and why
rhdh-jira-api 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH Jira API
One home for talking to Jira. The command syntax, the field IDs, the query patterns, and the workflow rules live here so that the create, refine, update, and sprint skills carry none of their own copies.
This skill reads. It never decides what to file and never approves a write — though it does define exactly what a write costs, because the payload shapes are here.
Route by question
| Question | Load |
|---|---|
Is Jira reachable? Is acli authenticated? |
references/auth.md, then uv run scripts/setup.py --json |
Which acli flag does this, and what breaks? |
references/acli-commands.md |
| What JQL answers this? Which board or sprint? | references/jql-patterns.md |
| Which custom field, label, link type, component, or priority? | references/fields.md |
| What must be true before this status transition? | references/workflows.md |
| I need a relationship-heavy bulk read or a team roster | references/graphql-queries.md |
acli cannot read or set this field |
references/rest-api-fallback.md |
Load the one branch the question needs.
The two traps that produce wrong answers
Both fail silently, and both have burned this pack before.
Default page size is 30. Rows past the thirtieth are dropped with no
warning, so a query that should return 140 issues quietly returns 30 and every
count built on it is wrong. Pass --limit 500 or --paginate on every bulk
search, and use --count first when the total matters.
Custom fields are absent unless you ask for them. search --json and
view KEY --json return only assignee, issuetype, priority, status, and
summary. Story Points, Team, Size, and Sprint come back empty — which looks
exactly like a field nobody set. Enrich with scripts/parse_issues.py --enrich
or view KEY --fields '*all' --json before claiming any of them is missing.
What ships with it
13 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 117 B
- references/acli-commands.md 8.6 KB
- references/auth.md 1.9 KB
- references/fields.md 17 KB
- references/graphql-queries.md 6.7 KB
- references/jql-patterns.md 5.7 KB
- references/rest-api-fallback.md 4.3 KB
- references/workflows.md 4.9 KB
- scripts/jira-wiki-to-adf.py 6.2 KB runs code
- scripts/parse_issues.py 12 KB runs code
- scripts/setup.py 5.0 KB runs code
- scripts/validate_components.py 5.6 KB runs code
- scripts/validate_field_ids.py 9.3 KB runs code
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 · 102 lines · 166 tokens per session scan A 775943f9bef7
rhdh-jira-api is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed today), licensed Apache-2.0. It adds 166 tokens to every session and 1,272 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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.