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-plugin-midstream-propagategit 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-plugin-midstream-propagate)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-plugin-midstream-propagate"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-plugin-midstream-propagate.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.00152 | $0.02395 |
| Opus 5 | $0.00076 | $0.01197 |
| Sonnet 5 | $0.00030 | $0.00479 |
| Haiku 4.5 | $0.00015 | $0.00239 |
Grade A, and why
rhdh-plugin-midstream-propagate 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH plugin → overlays → catalog propagate
Three-step chain after a fix or feature in redhat-developer/rhdh-plugins:
- Update rhdh-plugins with the change, including a changeset; wait until merged and new package(s) are published to npmjs.com (e.g.
@red-hat-developer-hub/backstage-plugin-app-defaults0.0.3and other packages published at the same time). - Update the overlays repo (
rhdh-plugin-export-overlays) to fetch the commit SHA for the Version Packages PR related to the above change. - Grab the specific changes from that SHA and push them into rhdh-plugin-catalog, updating
overlay-repo/,workspaces/, and other paths thatsync-midstream.shwould touch for a full clone of just that workspace; open an MR that applies the updated files and bumps associated PLR(s) in.tekton/to the appropriate tags (e.g.2.0.0--0.0.3).
Prefer a surgical catalog MR over build/ci/sync-midstream.sh --force-clone <workspace> (minutes vs a long full re-clone/export). Fall back to scoped --force-clone only when export / plugin_builds annotations / workspace transform must be regenerated.
Repos and config
| Step | Repo | Config key |
|---|---|---|
| 1 | redhat-developer/rhdh-plugins |
repos.plugins |
| 2 | redhat-developer/rhdh-plugin-export-overlays |
repos.overlay |
| 3 | gitlab.cee.redhat.com/rhidp/rhdh-plugin-catalog |
repos.catalog |
Resolve checkouts by invoking /rhdh-context by name and reading the paths it reports. To run its CLI directly instead, set RHDH to that skill's scripts/rhdh wrapper and use dot-notation keys: "$RHDH" --json config get repos.<key> | jq -r '.data.value' (see references/catalog-surgical-update.md). Use glab against gitlab.cee.redhat.com for catalog MRs (not gitlab.com).
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.
- 8d ago First seen · 123 lines · 152 tokens per session scan A f5b49fdaee54
rhdh-plugin-midstream-propagate is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 4d ago), licensed Apache-2.0. It adds 152 tokens to every session and 2,395 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.