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-schedulegit 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-schedule)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-release-schedule"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-release-schedule/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-schedule"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-release-schedule.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.00123 | $0.00471 |
| Opus 5 | $0.00062 | $0.00235 |
| Sonnet 5 | $0.00025 | $0.00094 |
| Haiku 4.5 | $0.00012 | $0.00047 |
Grade A, and why
rhdh-release-schedule 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.
What it actually says
RHDH release dates
Say when a milestone falls, and say which source said so. Read-only.
Route
Load workflows/release-dates.md. One workflow covers both sources: Jira for
releases already in flight, the schedule spreadsheet for anything further out.
Which one answers a given version is a lookup, not a decision the user makes.
Boundary with the neighbouring skills
- What is still open against a release is
/rhdh-release-status. - Drafting the Slack message that goes out at a freeze is
/rhdh-release-announce, which pulls the date it needs itself. - Which OCP, AKS, EKS, GKE, or PostgreSQL versions a release supports, and when
they go end-of-life, is
/rhdh-platform-lifecycle. Product lifecycle is not a release milestone. - Reading or editing the RHDHPLAN release Feature as a Jira issue is
/rhdh-jira-api.
Completion
Complete when every date reported names its source — the Jira release issue key or the schedule spreadsheet tab — and dates the two sources disagree on are shown side by side rather than silently reconciled. A milestone the source records as TBD is reported as TBD, never estimated from the surrounding dates or from a previous release's spacing. When a version appears in neither source, say so and ask for the exact version string as it appears in the sheet.
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 125 B
- 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-dates.md 3.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.
- 5d ago First seen · 42 lines · 123 tokens per session scan A 7817b8011df8
rhdh-release-schedule is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed today), licensed Apache-2.0. It adds 123 tokens to every session and 471 once invoked, about $0.0006 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.
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.