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-statusgit 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-status)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-release-status"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-release-status/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-status"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-release-status.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.00700 |
| Opus 5 | $0.00083 | $0.00350 |
| Sonnet 5 | $0.00033 | $0.00140 |
| Haiku 4.5 | $0.00017 | $0.00070 |
Grade A, and why
rhdh-release-status 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 5d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH release status
Answer "how is this release doing" with numbers that carry a Jira link and a timestamp. Read-only: this skill never edits Jira and never posts anything.
Route
Load workflows/release-status.md. It maps each question to the
scripts/release.py subcommand that answers it, and carries the two scope rules
the CLI output does not explain on its own.
For readiness at the Feature and Program Increment level rather than the issue
level — "are we ready to ship", PI funnel, dependency map, per-Feature coherence
— load references/feature-readiness.md instead. It runs quick mode for ceremony
prep and deep mode for full coherence analysis. Both are read-only.
Rich Filter ownership
This skill owns the Rich Filter configuration prose. references/config.md holds
the spreadsheet IDs, the discovery rule, and the RHDH_RICH_FILTER_PATH
override; references/rich-filter-coverage.md records which release behaviours
come from the export and which JQL stays local and why. Another skill that hits
an unavailable Rich Filter template names /rhdh-release-status rather than
restating the setup.
Boundary with the neighbouring skills
- Milestone dates — Feature Freeze, Code Freeze, GA — are
/rhdh-release-schedule. - A Slack freeze announcement is
/rhdh-release-announce. - The team roster, leads, and Cloud IDs are
/rhdh-release-teams. This skill counts issues per team; it does not publish the roster. - Reading a single issue, a board, or a sprint is
/rhdh-jira-api. Any Jira write is/rhdh-jira-update.
Completion
Complete when every number in the answer names the subcommand or JQL that produced it, states when it was read, and carries the Jira search link behind it. A count the CLI reported as truncated is reported as a floor, not a total. A field Jira could not supply is listed as unverified — never carried over from an earlier release or inferred from a neighbouring count. When the Rich Filter was unavailable, say which scopes went unanswered instead of substituting a hand-written query.
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 125 B
- references/config.md 2.4 KB
- references/feature-readiness.md 11 KB
- references/rich-filter-coverage.md 2.0 KB
- scripts/_jira.py 6.2 KB runs code
- scripts/_support.py 11 KB runs code
- scripts/jql-release.md 4.5 KB
- scripts/jql.py 7.0 KB runs code
- scripts/release.py 43 KB runs code
- scripts/rich_filter.py 15 KB runs code
- scripts/slack_templates.py 3.7 KB runs code
- scripts/slack-templates.md 7.1 KB
- workflows/release-status.md 4.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.
- 5d ago First seen · 58 lines · 166 tokens per session scan A fb74a24f09ce
rhdh-release-status 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 700 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-09-03.
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.