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 alimobrem/openshift-platform-skills --skill platform-infragit clone --depth 1 https://github.com/alimobrem/openshift-platform-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/alimobrem/openshift-platform-skills/platform-infra)<a href="https://agentmods.dev/skills/alimobrem/openshift-platform-skills/platform-infra"><img src="https://agentmods.dev/badge/skills/alimobrem/openshift-platform-skills/platform-infra/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/alimobrem/openshift-platform-skills/platform-infra"><img src="https://agentmods.dev/badge/skills/alimobrem/openshift-platform-skills/platform-infra.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.00112 | $0.01178 |
| Opus 5 | $0.00056 | $0.00589 |
| Sonnet 5 | $0.00022 | $0.00236 |
| Haiku 4.5 | $0.00011 | $0.00118 |
Grade A, and why
platform-infra 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 10d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenShift Infrastructure — Registry & Secrets
Skill for container image registries (Quay) and secrets management (External Secrets Operator) on OpenShift.
Rules
- Always use correct apiVersion and kind. Every CRD example must use the real apiVersion from the CRD table below. Never invent CRDs or apiVersions.
- Load references on-demand. Only read reference files when the user's question requires detailed field-level knowledge. Do not preload all references.
- Validate YAML before presenting. Every YAML example must be syntactically valid and use real field names from the CRD schemas.
- Prefer canonical patterns. Use patterns from reference docs as starting points. Adapt to the user's specifics rather than inventing from scratch.
- Ask about optional components when ambiguous. If the user's prompt does not specify which registry or secrets tool they use, ask before generating YAML with defaults.
How This Skill Works
| User asks about | Reference | Topic |
|---|---|---|
| Registry, Quay, Harbor, image push, robot accounts, scanning, Clair | references/quay.md |
Registry |
| Secrets, Vault, ESO, ExternalSecret, credentials, rotation, SecretStore | references/external-secrets.md |
Secrets |
Load the matching reference file before answering. Max 1 reference file per request.
Swappable Components
| Layer | Default | Alternatives |
|---|---|---|
| Registry | Quay | Harbor, OpenShift internal registry, ECR, GCR, GHCR, Docker Hub |
| Secrets | External Secrets Operator | Vault (direct), Sealed Secrets, SOPS, AWS Secrets Manager, Vault CSI |
Ask which components the user has if the prompt is ambiguous. Do not assume defaults without checking. When the user says "we use Harbor," generate Harbor-specific push secrets, robot accounts, and registry URLs instead of Quay equivalents.
CRD Reference Table
| Kind | apiVersion | Project |
|---|---|---|
| QuayRegistry | quay.redhat.com/v1 | Quay |
| SecretStore | external-secrets.io/v1 | ESO |
| ClusterSecretStore | external-secrets.io/v1 | ESO |
| ExternalSecret | external-secrets.io/v1 | ESO |
| ClusterExternalSecret | external-secrets.io/v1 | ESO |
What ships with it
3 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.
- 10d ago First seen · 103 lines · 112 tokens per session scan A 9c719f122bd7
platform-infra is a skill published in the GitHub repository alimobrem/openshift-platform-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 112 tokens to every session and 1,178 once invoked, about $0.0006 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-31.
Other skills, from other repositories
argocd
Operational skill for agents to implement GitOps with Argo CD - Applications, sync policies, AppProjects, health checks, and safe rollback.
k8s-design-validation
Validate Kubernetes-related design decisions. Use when checking resource requirements, deployment patterns, network design, and secret usage in the design.
dev-experience
Set up local development environment. Use when configuring devcontainers, workspace bootstrap, or local simulation.
gitops-overlay
Validate GitOps overlays for correctness and compliance. Use when reviewing kustomize builds, environment overlays, image tags, and secrets.
k8s-policy
Validate Kubernetes manifests for compliance. Use when reviewing resource limits, securityContext, network policies, and secret usage.
security-rbac
Validate RBAC, service accounts, and security posture. Use when reviewing roles, bindings, token permissions, and container security settings.