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 duyet/oma --skill dockerfilegit clone --depth 1 https://github.com/duyet/omaWrote 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/duyet/oma/dockerfile)<a href="https://agentmods.dev/skills/duyet/oma/dockerfile"><img src="https://agentmods.dev/badge/skills/duyet/oma/dockerfile/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/duyet/oma/dockerfile"><img src="https://agentmods.dev/badge/skills/duyet/oma/dockerfile.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.00087 | $0.01072 |
| Opus 5.5 | $0.00035 | $0.00429 |
| Sonnet 5.5 | $0.00017 | $0.00214 |
| Haiku 4.5 | $0.00009 | $0.00107 |
Grade D, and why
dockerfile scanned grade D with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Never run as root.** Create/`USER` a non-root user for the runtime stage — Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
&& rm -rf /var/lib/apt/lists/* How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dockerfile
Three things make a Dockerfile good: it builds fast on re-run (cache), the
image is small (multi-stage, slim base), and it runs safely (non-root,
no secrets baked in). Most Dockerfiles get all three wrong the same way — by
copying everything first and installing dependencies after. See
Dockerfile.example for an annotated multi-stage template.
Order layers by change frequency
Docker caches each instruction and invalidates everything after the first changed layer. So put what changes least on top, what changes most on the bottom. The classic win — install deps before copying source, because your lock file changes far less often than your code:
# GOOD — deps cached across every source-only change
COPY package.json package-lock.json ./
RUN npm ci
COPY . . # source changes don't bust the npm layer above
# BAD — every one-line code edit reinstalls all dependencies
COPY . .
RUN npm ci
(Same shape in any ecosystem: requirements.txt/pyproject.toml before the
Python source, go.mod/go.sum before the Go source, Cargo.toml before the
Rust source.)
Multi-stage: build fat, ship thin
Compile/install in a build stage with the full toolchain, then copy only the runtime artifacts into a clean, minimal final image. The compilers, dev headers, and caches never reach production.
FROM node:22 AS build
WORKDIR /app
COPY package.json package-lock.json ./
RUN npm ci
COPY . .
RUN npm run build
FROM node:22-slim AS runtime
WORKDIR /app
COPY package.json package-lock.json ./
RUN npm ci --omit=dev
COPY --from=build /app/dist ./dist
USER node
CMD ["node", "dist/server.js"]
Smaller and faster
- Pin the base image to a specific tag/digest (
node:22.4-slim, notnode:latest) — reproducible builds, no surprise breakage. Prefer-slimor-alpine(mind alpine's musl libc for native deps);distrolessfor a runtime with no shell/package manager at all. - One
RUNfor a package install + cleanup, so the cleanup lands in the same layer (deleting files in a later layer doesn't shrink the image):RUN apt-get update && apt-get install -y --no-install-recommends ca-certificates \ && rm -rf /var/lib/apt/lists/* .dockerignore— exclude.git,node_modules, build output,.env, test fixtures. It shrinks the build context (faster) and stops secrets and junk from being copied by a broadCOPY . ..- Use
COPY, notADD—ADDsilently auto-extracts archives and fetches URLs.COPYis predictable; reach forADDonly when you actually want those.
What ships with it
1 file 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 · 100 lines · 87 tokens per session scan D b619aeb2c19d
dockerfile is a skill published in the GitHub repository duyet/oma (10 stars, last pushed 9d ago), licensed Apache-2.0. It adds 87 tokens to every session and 1,072 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
k8s-networking
Kubernetes networking management for services, ingresses, endpoints, and network policies. Use when configuring connectivity, load balancing, or network isolation.