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-triggergit 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-trigger)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-prow-trigger"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-prow-trigger.svg" alt="Measured on agentmods" 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.00140 | $0.00802 |
| Opus 5 | $0.00070 | $0.00401 |
| Sonnet 5 | $0.00028 | $0.00160 |
| Haiku 4.5 | $0.00014 | $0.00080 |
Grade A, and why
rhdh-prow-trigger 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger an RHDH nightly ProwJob
Execute a job that is already configured in openshift/release. This skill never
edits CI configuration: changing which jobs exist is /rhdh-prow-jobs for test
entries and pools, and /rhdh-prow-release-branch for a release branch's whole
job set.
Route
Load workflows/trigger-nightly.md. It covers listing jobs, mapping a
natural-language request to a full job name, the override options, and execution.
Authentication
scripts/trigger_nightly_job.py uses a dedicated kubeconfig at
~/.config/openshift-ci/kubeconfig so it never disturbs the user's current
cluster context. It consumes an existing oc session and never performs a login.
When oc is missing, the dedicated kubeconfig is absent, or the session has
expired, stop and tell the user to run /setup-rhdh-skills openshift-ci. Setup
owns login; this skill does not.
The public script hands scripts/gangway_adapter.py only a kubeconfig path and
the request payload. That adapter alone retrieves the transient credential and
authenticates the request, and returns credential-free response data. Keep
tokens out of arguments, output, and anything reported back.
Execution rules
Triggering a job is an external write; --dry-run and --list are not. Follow
/mutation-gate, with the full job name as the target.
- Preview with
--dry-runfirst. It prints the adapter request without executing. - The preview carries the full command, the parameters, what the run will cost
and touch, and how to abort it. Get explicit approval before running without
--dry-run. - GKE and OSD-GCP each share one cluster. Never start a second job on the same platform while one is running; warn the user before triggering either.
- Approval to inspect or dry-run is not approval to execute. Ask again.
--image-reporequires--tag;--tagworks alone.--playwright-versionis overlay-only. Image, chart, and alert overrides are rejected for overlay jobs.
Completion
A trigger is complete when the executed command is shown exactly as run, the
Gangway API response is reported, and the run URL or ID is stated prominently —
or, when the API returned no identifier, that absence is stated rather than
implied. A dry run is complete when the printed request is shown and it is clear
that nothing was executed. A failure is complete when the error is reported with
its likely cause, expired authentication being the common one, and the user is
pointed at /setup-rhdh-skills openshift-ci when the session is the problem. No
credential appears in any of it.
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.
- 7d ago First seen · 67 lines · 140 tokens per session scan A 161f8bab45ec
rhdh-prow-trigger is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 140 tokens to every session and 802 once invoked, about $0.0007 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.