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-linkgit 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-link)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-jira-link"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-jira-link/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-link"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-jira-link.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 162 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 162 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00201 | $0.02623 |
| Opus 5 | $0.00101 | $0.01311 |
| Sonnet 5 | $0.00040 | $0.00525 |
| Haiku 4.5 | $0.00020 | $0.00262 |
Grade A, and why
rhdh-jira-link 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 7d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira PR / MR links
Zero-token Node scripts for GitHub and GitLab: create the PR/MR, attach a Jira remote Web link, post or update a structured comment, and optionally fill empty issue fields.
Scripts live under this skill's scripts/ directory. Resolve that path from the
installed skill root (agents already have it when reading this file):
SKILL="$(cd "$(dirname "$0")" && pwd)" # or the absolute path to this skill root
node "$SKILL/scripts/create-pr-mr.js" …
node "$SKILL/scripts/link-pr-mr.js" …
Another skill that needs the link step invokes /rhdh-jira-link by name and
lets this skill run its own scripts; it never calls into this directory by path.
Preferred: one-shot create (create-pr-mr.js)
After the feature branch is committed:
Compose the reviewer-facing PR or MR title and body, then invoke
/prose-editing once on both in the flavored register. Preserve Jira keys,
closing syntax, headings, checklists, links, and the required Generated-by
line. Pass the edited strings to create-pr-mr.js; it is a transport layer and
must not edit them. The structured Jira link comment created later is a protocol
payload and does not receive this prose pass.
node "$SKILL/scripts/create-pr-mr.js" \
--issue RHIDP-12345 \
--title 'fix: short summary' \
--target main \
--body "$(cat <<'EOF'
## Summary
- …
## Test plan
- [ ] …
Generated-by: cursor
EOF
)"
git push -u origin HEAD(unless--no-push)- Detects GitHub vs GitLab from
origin - Runs
gh pr createorglab mr create - Runs
link-pr-mr.js link(unless--no-link). Missing Jira auth is an error; pass--no-linkto skip linking. - Opens the diffs page (unless
--no-open)
Flags: --draft, --no-push, --no-link, --no-open, --no-defaults,
--no-comment, --no-jira-ref, --host github|gitlab.
Auth
Either works (same token either way):
JIRA_API_TOKEN+login/serverin~/.config/.jira/.config.yml, or.jira-token(email:token) next toacli— the same credential/rhdh-jira-apiuses. Invoke/rhdh-jira-apiby name for the authoritative auth setup instead of duplicating it here.
What ships with it
7 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.
- 7d ago Changed · +5 lines · +8 tokens per session a7547eb86ba8
- 11d ago First seen · 232 lines · 193 tokens per session scan A 610082496429
rhdh-jira-link is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 2d ago), licensed Apache-2.0. It adds 201 tokens to every session and 2,623 once invoked, about $0.0010 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.