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-pr-creategit 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-pr-create)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-pr-create"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-pr-create.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.00103 | $0.01112 |
| Opus 5 | $0.00051 | $0.00556 |
| Sonnet 5 | $0.00021 | $0.00222 |
| Haiku 4.5 | $0.00010 | $0.00111 |
Grade A, and why
rhdh-pr-create 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH Pull Request
Own publication after implementation is verified. Accept either the current staged checkout or a change handoff from the calling skill; do not diagnose or modify product code.
Start here
- Load
references/repo-profiles.mdand identify the canonical upstream from all remotes. - Run
gh auth statusand inspect branch, status, staged diff, and upstream default branch. - If the calling skill supplied a change handoff, validate its repository and file list, issue reference, recordings, and verification evidence against the checkout. Treat the checkout as authoritative and report mismatches.
- Follow
workflows/create-pull-request.mdsequentially. There is no auto-approve mode: every external write is stated in full and approved as that stated set before it runs.
Boundaries
- This skill stages, formats, validates, creates changesets, commits, pushes,
opens the PR, uploads supplied recordings, and updates linked GitHub issues.
Jira reads belong to
/rhdh-jira-apiand Jira writes to/rhdh-jira-update. Invoke either by name and consume what it reports; never call Jira directly from here. - GitHub issue reads belong to
/rhdh-forge, which returns the same issue detail withsource: github. Loadreferences/github-input.mdwhen the request supplies an issue URL or number. - It does not implement fixes or features. If validation exposes a product-code
failure, stop and hand the failure back to the skill that produced the change,
usually
/rhdh-plugin-bug-fix, with the failing command and its output. - Pre-existing dirty or untracked files are outside the publication set unless the user explicitly identifies them as part of the change.
- Only published plugin source paths need changesets; private
packages/*, dev apps, tests, fixtures, and stories do not. - Never fabricate issue data, recording URLs, CI results, or reviewer evidence.
Change handoff
A skill that produced a verified change may hand it off instead of leaving it
staged; /rhdh-plugin-bug-fix is the usual producer. The handoff arrives in the
conversation and names the change summary, the file list making up the change,
the issue reference, the optional before and after recordings, and the
verification that was run with its result.
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 · 97 lines · 103 tokens per session scan A 811ffb0aaa4c
rhdh-pr-create is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,112 once invoked, about $0.0005 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".