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-test-plan-reviewgit 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-test-plan-review)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-test-plan-review"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-test-plan-review/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-test-plan-review"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-test-plan-review.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.00128 | $0.00866 |
| Opus 5 | $0.00064 | $0.00433 |
| Sonnet 5 | $0.00026 | $0.00173 |
| Haiku 4.5 | $0.00013 | $0.00087 |
Grade A, and why
rhdh-test-plan-review 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 6d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH test-plan review
Compare the version tables and key dates a test-plan issue carries against what the lifecycle sources and the release schedule actually say, then apply what the user accepts.
Read first. Nothing reaches Jira until the user has walked the diff row by row and approved a stated set of writes.
Route
- Resolve the plan key or URL and the target RHDH version.
- Load
workflows/review-test-plan.mdand follow it end to end. - Load
references/sources.mdat Step 4 — it holds every lifecycle URL and the extraction rules per product. - Load
references/google-sheets-setup.mdonly when schedule access fails.
Named-skill handoffs
Invoke each by name and use what it reports. Never read, execute, or locate a sibling skill's files. When a named skill is absent, say so and name the review dimension that stays unverified.
| Need | Skill |
|---|---|
| The plan issue, its linked issues, ownership, labels, and status | /rhdh-jira-api |
| Supported OCP, Kubernetes, PostgreSQL, RHBK, and Quay versions | /rhdh-platform-lifecycle |
| Feature Freeze, Code Freeze, and GA dates | /rhdh-release-schedule |
| What is still open against the release | /rhdh-release-status |
| Editing the plan description or posting a comment | /rhdh-jira-update |
| Creating a child task | /rhdh-jira-create |
scripts/check_gsheets.py and scripts/fetch_schedule.py are this skill's own
schedule adapters, not cross-skill interfaces. gog keeps Google credentials
behind its native interface.
What the review reports
State the plan key and the release version, then, for every platform and integration row and every key date:
- the current value, the suggested value, and the lifecycle or schedule source behind the suggestion;
- rows left unchanged, and why;
- rows the review could not evaluate, naming the source or skill that was unavailable.
A row with no suggested version is a gap. A row whose source could not be read is unverified. Neither may be dropped, and neither may be reported as the other.
What ships with it
6 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.
- 6d ago First seen · 80 lines · 128 tokens per session scan A 32461543be4b
rhdh-test-plan-review is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed yesterday), licensed Apache-2.0. It adds 128 tokens to every session and 866 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
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.