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-placementgit 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-placement)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-test-placement"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-test-placement/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-placement"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-test-placement.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.00162 | $0.00999 |
| Opus 5 | $0.00081 | $0.00500 |
| Sonnet 5 | $0.00032 | $0.00200 |
| Haiku 4.5 | $0.00016 | $0.00100 |
Grade A, and why
rhdh-test-placement 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 9d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH Test Placement
Advisory only. This skill answers where a lasting test belongs and what it should be modelled on. It does not write the test, run it, or change a file. The guiding rule: pick the cheapest environment that can actually catch the bug. Most plugin validation needs no cluster, and a growing share needs no Docker either.
Prerequisite: /grilling
Placement is a tradeoff, not a lookup. Cost, feedback time, coverage overlap, and what a layer can physically observe all pull in different directions, and the person asking usually has a preferred answer already.
Invoke /grilling before recommending a placement, and use the constraints
it produces. If /grilling is not installed, stop: say the skill is required,
name /setup-rhdh-skills install as the human's next step, and do not guess a
placement in the meantime.
Scope
| In scope | Out of scope |
|---|---|
| Where a permanent regression or coverage test belongs | Writing or running the test |
| Which repository and layer, and why not the others | Fixing the defect under test |
| Which existing file to mirror | A throwaway reproduction test |
| The rough feedback cost of each candidate | Reviewing an RHDH Jira test plan |
A one-off test that reproduces a defect and is then deleted is not this skill's
subject; /rhdh-plugin-bug-fix owns that and removes the file before handing
its change off. Come here for the durable test that stays behind afterwards.
Route by outcome
| Outcome | Load and follow |
|---|---|
| Recommend a repository, layer, harness, and template | references/test-placement.md |
references/test-placement.md carries the context questions to settle first,
the repository decision table, the L1–L4b layer ladder, per-placement authoring
notes with the file to copy, the commands that run each layer, and the things
that are researched as not possible today.
Boundaries
/grillingis a hard prerequisite, not an option./rhdh-plugin-authoringowns writing the recommended test once the placement is settled./rhdh-plugin-bug-fixowns the throwaway reproduction and its evidence./rhdh-test-plan-reviewreviews an RHDH release test plan in Jira. That is a release-readiness review, not a placement question.
What ships with it
2 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.
- 9d ago First seen · 91 lines · 162 tokens per session scan A ea0ecc654315
rhdh-test-placement is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed today), licensed Apache-2.0. It adds 162 tokens to every session and 999 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
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.