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-prow-release-branchgit 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-prow-release-branch)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-prow-release-branch"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-prow-release-branch/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-prow-release-branch"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-prow-release-branch.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.00168 | $0.01005 |
| Opus 5 | $0.00084 | $0.00502 |
| Sonnet 5 | $0.00034 | $0.00201 |
| Haiku 4.5 | $0.00017 | $0.00101 |
Grade A, and why
rhdh-prow-release-branch 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 11d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH release-branch Prow configuration
Turn the CI configuration for one release-{version} branch of
redhat-developer/rhdh on or off in openshift/release. Both directions need a
local checkout because both end in make update.
This skill is about Prow configuration, not about the product release. What is
open against a release is /rhdh-release-status, its milestone dates are
/rhdh-release-schedule, and its freeze announcement is /rhdh-release-announce.
Individual test entries and cluster pools on a branch that already has jobs
belong to /rhdh-prow-jobs.
Route
| Intent | Load |
|---|---|
| Create CI configuration for a new release branch | workflows/commission-release.md |
| Remove CI configuration for an end-of-life release branch | workflows/decommission-release.md |
references/release-branch-config.md holds the file paths, the release-vs-main
differences, and the Slack alert setup that both workflows use. Read it with
whichever workflow you loaded.
Local preparation and publication
Creating the local review branch, copying or deleting the config, editing
_prowconfig.yaml, and running make update are local preparation authorized by
the user's commission or decommission request. Make and validate those local
changes without a write gate.
Follow /mutation-gate for commit, push, and pull request creation only. Treat
them as one ordered publication set, name every reviewed path and external
target, and stop before each later operation when an earlier one fails.
- Never hardcode the branch-protection block or the release-branch adjustments. Read the latest existing release branch and copy its current shape; required status-check contexts and presubmit settings change over time.
- Confirm the version-specific values with the user before finalizing: which OCP
test entries to include,
MAPT_KUBERNETES_VERSION, the OSD version,releases.latest.release, and thebuild_roottag. - Decommissioning is destructive. Name every file and block to be removed, and the rollback, before removing anything.
- The Slack channel, its incoming webhook, and the Vault key
SLACK_ALERTS_WEBHOOK_URL_{X}_{Y}are human steps outside the repository. Ask the user to perform them; do not treat the config change as finished whilereporter_config.channelpoints at a channel that does not exist.
What ships with it
4 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.
- 11d ago First seen · 81 lines · 168 tokens per session scan A c700743c6ffe
rhdh-prow-release-branch is a skill published in the GitHub repository redhat-developer/rhdh-skills (17 stars, last pushed 2d ago), licensed Apache-2.0. It adds 168 tokens to every session and 1,005 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
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.