Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/napalmpapalam/skillsnpx agentmods add skills/napalmpapalam/skills/dockerfileWrote 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/napalmpapalam/skills/dockerfile)<a href="https://agentmods.dev/skills/napalmpapalam/skills/dockerfile"><img src="https://agentmods.dev/badge/skills/napalmpapalam/skills/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/napalmpapalam/skills/dockerfile"><img src="https://agentmods.dev/badge/skills/napalmpapalam/skills/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.00106 | $0.01597 |
| Opus 5 | $0.00053 | $0.00798 |
| Sonnet 5 | $0.00021 | $0.00319 |
| Haiku 4.5 | $0.00011 | $0.00160 |
Grade D, and why
dockerfile scanned grade D with 3 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 4d 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.
Containers run as root by default. A container escape then starts from root on the host. 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/* Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
&& apt-get install -y --no-install-recommends curl ca-certificates \ How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dockerfile Rules
Four goals, in this order: correct runtime, small image, fast cache, no secrets in layers. A layer is immutable — anything a layer writes ships in the image, even if a later layer deletes it.
Base image
- Pick the smallest base that runs the artifact:
- Distroless — compiled binaries with no shell needed. Smallest attack surface.
- Alpine — static binaries, Go, Rust. musl, so check C dependencies first.
- Slim — Python, Node.js. Debian userland without the build toolchain.
- Pin an exact tag. Never
latest— the build stops being reproducible the moment upstream moves. - Pin the digest when the build must be byte-identical:
node:22.11.0-alpine@sha256:….
FROM node:22.11.0-alpine # good — deterministic
FROM node:latest # bad — a different image every rebuild
Build context
The daemon receives the whole context directory before the build starts. A large context slows every build, even a fully cached one.
- Keep the context to the directory the build actually reads.
- Always write a
.dockerignore. It cuts upload time and keeps secrets out of the image.
.git
node_modules
target
dist
*.log
.env
.env.*
**/*.pem
Layer cache
Docker invalidates a layer and every layer after it when its inputs change. So order the file by change frequency: rarely-changed inputs first, source code last.
- Copy the manifests, install dependencies, then copy the source. Source edits then reuse the dependency layer.
COPY package.json package-lock.json ./
RUN npm ci # cached until the manifests change
COPY . . # invalidated by every source edit
- Chain one
RUNper logical step with&&and\. Clean the package cache inside the sameRUN— a separateRUN rmleaves the files in the earlier layer.
RUN apt-get update \
&& apt-get install -y --no-install-recommends curl ca-certificates \
&& rm -rf /var/lib/apt/lists/*
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.
- 4d ago First seen · 168 lines · 106 tokens per session scan D 9e11fd930a3f
dockerfile is a skill published in the GitHub repository napalmpapalam/skills (4 stars, last pushed 5d ago), licensed MIT. It adds 106 tokens to every session and 1,597 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-13.
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…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
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.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
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.