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-platform-lifecyclegit 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-platform-lifecycle)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-platform-lifecycle"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-platform-lifecycle.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.00143 | $0.00736 |
| Opus 5 | $0.00072 | $0.00368 |
| Sonnet 5 | $0.00029 | $0.00147 |
| Haiku 4.5 | $0.00014 | $0.00074 |
Grade A, and why
rhdh-platform-lifecycle 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH platform support
Produce lifecycle facts without changing repositories or external systems.
Route
| Question | Load | Run |
|---|---|---|
| RHDH support and compatible OCP versions | workflows/check-rhdh.md |
scripts/check_rhdh_lifecycle.py |
| OpenShift support phases | workflows/check-ocp.md |
scripts/check_ocp_lifecycle.py |
| Azure AKS support and configured versions | workflows/check-aks.md |
scripts/check_aks_lifecycle.py |
| AWS EKS support and configured versions | workflows/check-eks.md |
scripts/check_eks_lifecycle.py |
| Google GKE support | workflows/check-gke.md |
scripts/check_gke_lifecycle.py |
| PostgreSQL support | workflows/check-pg.md |
scripts/check_pg_lifecycle.py |
| RHBK, Quay, or another Red Hat product | workflows/check-redhat.md |
scripts/check_lifecycle.py |
Load one workflow. Use the bundled script for deterministic retrieval and classification; add judgment only after its output is available.
What to report
Report, for the product asked about and the date the answer was produced:
- each version with the support phase and the source date the script returned;
- versions found only in
openshift/release, labelled configured, never supported; - the RHDH-to-platform compatibility pairs, where the script emits them;
- every endpoint the answer rests on;
- every version the script could not classify, as a warning.
Preserve the script's source dates and uncertainty. Distinguish vendor lifecycle
from versions merely configured in openshift/release. Do not infer that a
configured version is supported.
Composition
Other skills invoke /rhdh-platform-lifecycle by name and use what it reports.
rhdh_lifecycle is a private, local adapter: no other skill imports it or
locates this skill on disk, and all repository and YAML access stays behind it.
Completion
Complete when every product and version named in the request carries the support
phase and the source date the script returned, the answer names each endpoint it
rests on, and every version the script could not classify is reported as a
warning rather than dropped or estimated. A version found only in
openshift/release is reported as configured and never as supported. If a
lifecycle source was unreachable, name the product that remains unassessed
instead of returning the partial list as the answer.
What ships with it
23 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.
- agents/openai.yaml 123 B
- scripts/check_aks_lifecycle.py 4.6 KB runs code
- scripts/check_eks_lifecycle.py 6.0 KB runs code
- scripts/check_gke_lifecycle.py 2.9 KB runs code
- scripts/check_lifecycle.py 3.9 KB runs code
- scripts/check_ocp_lifecycle.py 3.1 KB runs code
- scripts/check_pg_lifecycle.py 1.9 KB runs code
- scripts/check_rhdh_lifecycle.py 2.8 KB runs code
- scripts/rhdh_lifecycle/__init__.py 66 B runs code
- scripts/rhdh_lifecycle/configured_versions.py 2.2 KB runs code
- scripts/rhdh_lifecycle/ocp.py 3.4 KB runs code
- scripts/rhdh_lifecycle/openshift_release.py 5.3 KB runs code
- scripts/rhdh_lifecycle/pg.py 3.1 KB runs code
- scripts/rhdh_lifecycle/redhat.py 6.2 KB runs code
- scripts/rhdh_lifecycle/rhdh.py 1.5 KB runs code
- scripts/rhdh_lifecycle/versions.py 2.1 KB runs code
- workflows/check-aks.md 917 B
- workflows/check-eks.md 1.0 KB
- workflows/check-gke.md 808 B
- workflows/check-ocp.md 1.4 KB
- workflows/check-pg.md 1.1 KB
- workflows/check-redhat.md 1.7 KB
- workflows/check-rhdh.md 1.1 KB
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 · 62 lines · 143 tokens per session scan A 05b7a14266bb
rhdh-platform-lifecycle is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 143 tokens to every session and 736 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…