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-release-fixversionsgit 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-release-fixversions)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-release-fixversions"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-release-fixversions/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-release-fixversions"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-release-fixversions.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.00133 | $0.01945 |
| Opus 5.5 | $0.00053 | $0.00778 |
| Sonnet 5.5 | $0.00027 | $0.00389 |
| Haiku 4.5 | $0.00013 | $0.00194 |
Grade A, and why
rhdh-release-fixversions 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 19d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH release fix versions
Keep the same fix-version names and metadata on RHIDP, RHDHPLAN, and RHDHBUGS. Most engineers never need this; release managers use it when spinning up or closing a release stream.
This skill is self-contained: its CLI lives here only. Other release skills do not embed these commands.
Run every command from this skill's directory (the folder that contains
SKILL.md), not the rhdh-skills repository root:
cd skills/release/rhdh-release-fixversions # in a checkout
# or cd to the installed rhdh-release-fixversions skill folder
uv run scripts/fixversions.py check --json
Route
Load workflows/sync-fixversions.md. Load references/version-fields.md when
metadata disagrees and you need field semantics or the canonical-source rule.
Load references/staging-jira.md when the human wants staging credentials or
--staging on the CLI.
| Intent | CLI |
|---|---|
| Verify auth and project access | uv run scripts/fixversions.py check --json |
| Try staging before production | add --staging to any command (including apply) |
| List unreleased versions (default) | uv run scripts/fixversions.py list --json |
| Lifecycle for one version across projects | uv run scripts/fixversions.py status VERSION --json |
| Before closing the release Feature | uv run scripts/fixversions.py close-check VERSION --json |
| Drift among unreleased versions (default) | uv run scripts/fixversions.py diff --json |
| Include recently released GA (365d window) | add --include-released to list, diff, or plan |
| Full historical inventory | add --all-versions to list, diff, or plan |
| Plan creates and updates for unreleased | uv run scripts/fixversions.py plan --json |
| Plan specific versions (with optional date overrides) | uv run scripts/fixversions.py plan --names 1.10.6,2.2.0 --release-date 2027-03-10 --json |
| Ensure one version everywhere | uv run scripts/fixversions.py ensure VERSION --json |
| Apply an approved plan | uv run scripts/fixversions.py apply --plan FILE --json |
What ships with it
10 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 134 B
- references/staging-jira.md 1.3 KB
- references/version-fields.md 6.6 KB
- scripts/_auth.py 5.8 KB runs code
- scripts/_fixversions_core.py 24 KB runs code
- scripts/_release_dates.py 3.8 KB runs code
- scripts/_stream_lifecycle.py 2.3 KB runs code
- scripts/_stream_versions.py 1.0 KB runs code
- scripts/fixversions.py 28 KB runs code
- workflows/sync-fixversions.md 5.7 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.
- 19d ago Changed · +16 lines 2eb39a43f1ea
- 1mo ago First seen · 125 lines · 133 tokens per session scan A bd59c61204ed
rhdh-release-fixversions is a skill published in the GitHub repository redhat-developer/rhdh-skills (18 stars, last pushed today), licensed Apache-2.0. It adds 133 tokens to every session and 1,945 once invoked, about $0.0005 per session on Opus 5.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-09-18.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.