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-bug-fixgit 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-bug-fix)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-plugin-bug-fix"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-plugin-bug-fix.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.00149 | $0.01039 |
| Opus 5 | $0.00075 | $0.00519 |
| Sonnet 5 | $0.00030 | $0.00208 |
| Haiku 4.5 | $0.00015 | $0.00104 |
Grade A, and why
rhdh-plugin-bug-fix 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 7d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH Plugin Bug Fix
Own the path from a bug report to a verified fix. Reproduce before diagnosing, diagnose before editing, and verify before reporting. The reproduction test is diagnostic evidence and never ships.
Start here
Follow workflows/fix-bug.md from the top. It resolves the issue reference,
triages the report for agent readiness, discovers the workspace, picks the
full-e2e or no-e2e branch, reproduces, fixes, verifies, and cleans up.
Route by outcome
| Outcome | Load and follow |
|---|---|
| Reproduce, diagnose, and fix a plugin bug | workflows/fix-bug.md |
| Resolve a report to a plugin workspace | references/workspace-map.md |
| Author the temporary Playwright reproduction | references/e2e-patterns.md |
| Capture and convert before and after evidence | references/video-recording.md |
Boundaries
/rhdh-forgeowns reading GitHub. Invoke it by name with the raw issue or pull request reference and consume the structured issue context it returns — key, summary, URL, repository, number, state, labels, description, and the candidate workspace with the strategy that resolved it. Confirm that workspace against the checkout before working in it, and ask the user when the strategy reports it unresolved. Do not parse the URL or rungh issue viewhere./rhdh-jira-apiowns reading a Jira key and returns the same issue detail./grillingis the design gate when several root causes remain plausible or materially different fixes carry different compatibility costs. Use the constraints it produces before implementing. If it is not installed, say so, name/setup-rhdh-skills installas the human's next step, and pause that branch./rhdh-test-placementadvises where a permanent regression test belongs. The reproduction test written here is throwaway and is deleted before the change is handed off./rhdh-plugin-authoringowns feature work and public API design./rhdh-pr-createowns staging, changesets, commits, pushes, pull requests, recording uploads, and issue updates.
What ships with it
5 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.
- 7d ago First seen · 88 lines · 149 tokens per session scan A 39ab984ce20d
rhdh-plugin-bug-fix is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 149 tokens to every session and 1,039 once invoked, about $0.0007 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.