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 Miaoge-Ge/coding-agent-skills --skill docker-expertgit clone --depth 1 https://github.com/Miaoge-Ge/coding-agent-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/miaoge-ge/coding-agent-skills/docker-expert)<a href="https://agentmods.dev/skills/miaoge-ge/coding-agent-skills/docker-expert"><img src="https://agentmods.dev/badge/skills/miaoge-ge/coding-agent-skills/docker-expert/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/miaoge-ge/coding-agent-skills/docker-expert"><img src="https://agentmods.dev/badge/skills/miaoge-ge/coding-agent-skills/docker-expert.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.00086 | $0.00993 |
| Opus 5.5 | $0.00034 | $0.00397 |
| Sonnet 5.5 | $0.00017 | $0.00199 |
| Haiku 4.5 | $0.00009 | $0.00099 |
Grade C, and why
docker-expert scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Combine related `RUN` steps and clean caches **in the same layer** (`apt-get … && rm -rf /var/lib/apt/lists/*`) — a separate cleanup layer doesn't shrink the image. How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Expert
Small, reproducible, non-root, cache-friendly. Order layers from least- to most-changing, build in one stage and ship artifacts from another, and never bake secrets into the image.
When to Use
- Writing or optimizing a Dockerfile.
- Reducing image size, speeding builds, or fixing cache busting.
- Multi-service local dev with Compose.
- Container networking, volumes, signals, or startup issues.
When NOT to Use
- Cluster orchestration, scaling, rollouts, probes →
kubernetes-expert. - The app code itself → the relevant language skill.
- CI pipeline YAML →
github-master.
Core Principles
1. Small & secure base
- Minimal, pinned bases:
node:22.4-slim,python:3.12-slim, Alpine, or distroless for runtime. Never:latest(non-reproducible). - Run as a non-root user (
USER). Copy only what's needed; add a.dockerignore(.git,node_modules, build output, secrets) to shrink the build context and avoid leaking files.
2. Cache-efficient layers
- Order instructions least- → most-frequently-changing. Copy dependency manifests and install before copying source, so editing code doesn't bust the dependency layer.
- Combine related
RUNsteps and clean caches in the same layer (apt-get … && rm -rf /var/lib/apt/lists/*) — a separate cleanup layer doesn't shrink the image. - Use BuildKit cache mounts (
RUN --mount=type=cache) for package managers; pass secrets via--mount=type=secret, neverARG/ENV.
3. Multi-stage builds
- Heavy build/compile stage → copy only artifacts into a lean runtime stage. Drops compilers, dev deps, and source from the final image (often 5–20× smaller).
4. Correct runtime
- One concern per container. Use exec-form
CMD/ENTRYPOINT(["node","server.js"]) so signals (SIGTERM) reach the process for graceful shutdown; add--initortiniif your process doesn't reap children. - Add a
HEALTHCHECK. Configure via env; persist data in volumes, not the writable layer.
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 · 77 lines · 86 tokens per session scan C 59826b608d0b
docker-expert is a skill published in the GitHub repository Miaoge-Ge/coding-agent-skills (7 stars, last pushed 4mo ago), licensed MIT. It adds 86 tokens to every session and 993 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (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
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says. Use when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line closers, staged openers, forced triads, dashes everywhere, inflated claims, sales language, stock AI words, bold labels, or filler. Based on Wikipedia's…
release-ota-promote
Publish signed Electron UI/daemon bundles to a local OTA feed with atomic manifest switch and digest readback, while dry-running the K8s drainrespawn rollout. Prod is refused before writes; feed publication is not client apply.
devops-infrastructure
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.
deploy-gen
Generate deployment configurations (Docker, Kubernetes) for the current project.