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 rhtevan/agentfs --skill ocp-containerfilegit clone --depth 1 https://github.com/rhtevan/agentfsWrote 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/rhtevan/agentfs/ocp-containerfile)<a href="https://agentmods.dev/skills/rhtevan/agentfs/ocp-containerfile"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/ocp-containerfile/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/rhtevan/agentfs/ocp-containerfile"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/ocp-containerfile.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.00028 | $0.01543 |
| Opus 5.5 | $0.00011 | $0.00617 |
| Sonnet 5.5 | $0.00006 | $0.00309 |
| Haiku 4.5 | $0.00003 | $0.00154 |
Grade A, and why
ocp-containerfile 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenShift Containerfile Best Practices
Audit existing Containerfiles or generate new ones that comply with
Red Hat OpenShift security constraints and container certification
requirements. Supports three modes targeting different OpenShift SCC
models: legacy (restricted-v2, OCP 4.11–4.19), user namespaces
(restricted-v3, OCP 4.20+), or both for backward compatibility.
This skill references the ocp-containerfile knowledge bundle at
~/.agents/knowledge/ocp-containerfile/ for detailed explanations
of each rule. The skill handles the procedural workflow; the
knowledge bundle provides the "why."
Prerequisites
bashfor audit and generate scriptspodmanfor image verification (verify mode only)- A project directory with application source (generate mode)
Modes
| Mode | Flag | Target SCC | When to Use |
|---|---|---|---|
legacy |
--mode legacy |
restricted-v2 |
OCP 4.11–4.19 clusters only |
userns |
--mode userns |
restricted-v3 |
OCP 4.20+ with user namespaces |
both |
--mode both |
Both | Default. Backward compat across versions |
If the user doesn't specify a mode, default to both.
Steps
1. Determine Operation
Ask the user what they need:
| User Intent | Operation |
|---|---|
| "audit my containerfile", "check containerfile" | Audit — lint existing Containerfile |
| "generate containerfile", "create containerfile" | Generate — create from CWD |
| "verify image", "check image" | Verify — inspect a built image |
2. Select Mode
Ask which OpenShift version range the image targets. If unclear,
use both (default).
3. Execute
Audit
bash ~/.agents/skills/ocp-containerfile/scripts/audit.sh \
--mode <legacy|userns|both> \
--file <path-to-containerfile>
Review the output. For each ❌ failure, explain the rule and provide the fix, referencing the knowledge bundle concepts.
Generate
bash ~/.agents/skills/ocp-containerfile/scripts/generate.sh \
--mode <legacy|userns|both> \
--output Containerfile
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.
- 1mo ago First seen · 164 lines · 28 tokens per session scan A eb0232bd3ff8
ocp-containerfile is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 1,543 once invoked, about $0.0001 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-09-17.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
bdd-container-update
Update the BDD test container image when its dependencies or runtime change. Determines version bump (major vs minor vs patch), rebuilds the Docker image, pushes to GitLab registry, and updates the image tag in starttest.sh. Test source (tests/, features/, scripts/, data/, conftest.py) is bind-mounted from the host…
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.