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-smoke-testsgit 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-smoke-tests)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-smoke-tests"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-smoke-tests/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-smoke-tests"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-smoke-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 17 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 39 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 77 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 121 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 114 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 121 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00228 | $0.02704 |
| Opus 5 | $0.00114 | $0.01352 |
| Sonnet 5 | $0.00046 | $0.00541 |
| Haiku 4.5 | $0.00023 | $0.00270 |
Grade A, and why
rhdh-smoke-tests 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH Helm and Operator smoke tests
Smoke test after an RC (Quay CI chart / IIB). Catalog-index OCI refs run first. Helm and Operator are both mandatory after that. One Helm namespace and one Operator namespace — the three checks are a chain in that namespace, not three installs.
This is not full QE, Prow e2e, local compose, or an operator-PR catalog test.
Route
- Collect tags. Stop if tags are missing — do not invent CI tags. Require
INDEX_IMAGEor deriveregistry.access.redhat.com/rhdh/plugin-catalog-index:${RC_VER}. RequireCATALOG_REPO(rhdh-plugin-catalog checkout that containsbuild/scripts/checkIndexRefsPullable.sh). - Catalog-index OCI check first, before any Helm install/upgrade or
Operator CSV work. Load
workflows/catalog-index.md. That agent getsCATALOG_REPOandINDEX_IMAGEonly (no kubeconfig). Wait until it finishes. A catalog fail does not skip Helm/Operator. - Establish
oc(login below). DeriveCLUSTER_ROUTER_BASEbefore Helm. - Default is an RC run. A GA run (published chart / OperatorHub
fast, includingfast↔fast-1.y) only when the user asked for GA. - Follow
/mutation-gateonce for both cluster chains (login + Helm + Operator). Then launch two agents in the same turn (Helm and Operator). Do not wait for Helm to finish before launching Operator. Do not run both cluster chains in the parent. Do not start them until step 2 has completed. - Load
workflows/helm.mdin the Helm agent,workflows/operator.mdin the Operator agent. - After every install or upgrade: Guest (below), then verify (below), then a live line (below).
| Load when | File |
|---|---|
| Catalog-index OCI (first) | workflows/catalog-index.md |
| Helm chain | workflows/helm.md |
| Operator chain | workflows/operator.md |
| Guest fragment | assets/app-config-guest.yaml |
| Helm Guest overlay | assets/helm-values-guest.yaml |
| Console URL → router / API | scripts/cluster_from_console.py |
What ships with it
9 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 129 B
- assets/app-config-guest.yaml 122 B
- assets/helm-values-guest.yaml 196 B
- scripts/cluster_from_console.py 2.6 KB runs code
- scripts/operator_upgrade.py 7.8 KB runs code
- scripts/verify_ns.py 7.6 KB runs code
- workflows/catalog-index.md 1.3 KB
- workflows/helm.md 2.4 KB
- workflows/operator.md 2.5 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 Changed · +26 lines · +26 tokens per session 5f1fb8d49e8d
- 6d ago First seen · 201 lines · 202 tokens per session scan A 005c9b324618
rhdh-smoke-tests is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed yesterday), licensed Apache-2.0. It adds 228 tokens to every session and 2,704 once invoked, about $0.0011 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.