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-operator-pr-testgit 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-operator-pr-test)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-operator-pr-test"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-operator-pr-test.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.00099 | $0.00683 |
| Opus 5 | $0.00049 | $0.00342 |
| Sonnet 5 | $0.00020 | $0.00137 |
| Haiku 4.5 | $0.00010 | $0.00068 |
Grade A, and why
rhdh-operator-pr-test 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 8d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH Operator PR Test
Deploy the PR's CI-built bundle onto a live cluster and verify the change there.
GitHub code review belongs to /rhdh-pr-review.
Start here
Follow workflows/test-operator-pr.md from the top. Load
references/operator-pr-images.md when extracting or validating CI image URLs.
Gates
| Gate | Required check | If fail |
|---|---|---|
| Forge | /rhdh-forge is installed and returns the PR |
Stop; name /setup-rhdh-skills install |
oc |
oc is on PATH |
Stop; name /setup-rhdh-skills |
| Cluster | oc whoami succeeds |
Stop; the human runs oc login, or follows the rhdh-test-instance provision path in the workflow |
| Repository | The PR is redhat-developer/rhdh-operator |
Stop; this skill tests that repository only |
Boundaries
/rhdh-forgeowns GitHub reads. Invoke it by name with the PR URL or number and consume repository, number, state, files, diff, head and base refs, and comments. Do not parse the URL here or copy a fetch workflow./rhdh-pr-reviewowns analyzing the diff for merge comments and posting a GitHub review./rhdh-localowns a local compose runtime, not a live OpenShift cluster./rhdh-overlayowns overlay PR artifact checks, not operator bundles./rhdh-contextlocates an RHDH checkout when a localrhdh-test-instancetree is needed. Do not add it as a catalog dependency.
Writes
Posting a /test comment, applying or deleting cluster resources, and deploying
or rolling back an RHDH instance are external writes: invoke /mutation-gate
and follow it. A cluster operation's target names the namespace; a comment's
target names the repository and PR number. A request to test approves no write.
Deploy the full PR bundle or manifests, not only the operator binary image. Preserve the original cluster state and report it with cleanup.
Completion
Complete when the report names the PR and images used, one result per live check, the overall verdict, the deployed bundle or manifests, original and final cluster state, rollback commands, cleanup status, and the outcome of every approved write including skipped ones. Do not cache cluster state inside the skill directory.
What ships with it
3 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.
- 8d ago First seen · 61 lines · 99 tokens per session scan A 0fd027b36bcf
rhdh-operator-pr-test is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 4d ago), licensed Apache-2.0. It adds 99 tokens to every session and 683 once invoked, about $0.0005 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
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipeline...
Checkly Monitoring as Code
Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.
CI Test Sharding Parallelization
Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.