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 agent-readinessgit 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/agent-readiness)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/agent-readiness"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/agent-readiness/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/agent-readiness"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/agent-readiness.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.00104 | $0.00463 |
| Opus 5.5 | $0.00042 | $0.00185 |
| Sonnet 5.5 | $0.00021 | $0.00093 |
| Haiku 4.5 | $0.00010 | $0.00046 |
Grade A, and why
agent-readiness 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 1mo 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.
What it actually says
RHDH Agent Readiness
Use an agentready report as the source of truth for repository-readiness work. The skill supports any git repository and adds RHDH context when the repository belongs to the RHDH ecosystem.
Principles
- Write assessment output to the OS temporary directory so reports never pollute the target repository.
- Apply only fixes supported by the report. Ask for project-specific facts; never invent architecture or design rationale.
- For a recognized RHDH repository, use
/rhdh-contextfor repository ownership, technology, key paths, and conventions. Continue generically when RHDH context is unavailable. - Treat a fresh post-change assessment as the completion criterion for every remediation run.
Route the request
| Request | Reference |
|---|---|
| Assess or improve one repository | references/assessment.md, then references/remediation.md when fixes are requested |
| Assess all RHDH repositories under a directory | references/batch.md |
When no path or mode is given, recommend the current repository as the default and offer batch assessment as the alternative.
Completion
- Assessment-only work is complete when the current score, certification, failing findings, and report location have been presented.
- Remediation work is complete when a fresh assessment shows the before/after result and every remaining failure is identified as unresolved, deferred, or inapplicable.
What ships with it
4 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.
- 1mo ago First seen · 49 lines · 104 tokens per session scan A 4feddb81ca70
agent-readiness is a skill published in the GitHub repository redhat-developer/rhdh-skills (18 stars, last pushed today), licensed Apache-2.0. It adds 104 tokens to every session and 463 once invoked, about $0.0004 per session on Opus 5.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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.