dockerfile

A set of practices for writing Dockerfiles, which are instruction files used to build runnable software containers. It covers build caching, multi-stage builds, smaller images, and safer execution.

In plain words
What is it for?
Use it to write, review, or improve a Dockerfile, containerize an application, reduce image size, or troubleshoot slow container builds.
Why use it?
It helps avoid slow rebuilds, unnecessarily large container images, and images that run with unsafe settings or contain secrets.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/duyet/oma/dockerfile
Any agent
npx skills add duyet/oma --skill dockerfile
Clone the repo
git clone --depth 1 https://github.com/duyet/oma

Made for: Claude Code, Codex.

Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,072 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00087 $0.01072
Opus 5 $0.00044 $0.00536
Sonnet 5 $0.00017 $0.00214
Haiku 4.5 $0.00009 $0.00107

Measured yesterday against content hash b619aeb2c19d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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/*
examples/skills/dockerfile/SKILL.md · 100 lines

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, not node:latest) — reproducible builds, no surprise breakage. Prefer -slim or -alpine (mind alpine's musl libc for native deps); distroless for a runtime with no shell/package manager at all.
  • One RUN for 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 broad COPY . ..
  • Use COPY, not ADDADD silently auto-extracts archives and fetches URLs. COPY is predictable; reach for ADD only when you actually want those.

Read the full file on GitHub · 100 lines

Files

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.

Changes

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.

  1. yesterday First seen · 100 lines · 87 tokens per session scan D b619aeb2c19d

Subscribe to this mod's changes

dockerfile is a skill published in the GitHub repository duyet/oma (5 stars, last pushed 12d ago), licensed Apache-2.0. It adds 87 tokens to every session and 1,072 once invoked, about $0.0004 per session on Opus 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens