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 sigistry/marketplace --skill dockerfile-smellsgit clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/sigistry/marketplace/dockerfile-smells)<a href="https://agentmods.dev/skills/sigistry/marketplace/dockerfile-smells"><img src="https://agentmods.dev/badge/skills/sigistry/marketplace/dockerfile-smells/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/sigistry/marketplace/dockerfile-smells"><img src="https://agentmods.dev/badge/skills/sigistry/marketplace/dockerfile-smells.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.00076 | $0.00812 |
| Opus 5 | $0.00038 | $0.00406 |
| Sonnet 5 | $0.00015 | $0.00162 |
| Haiku 4.5 | $0.00008 | $0.00081 |
Grade B, and why
dockerfile-smells scanned grade B 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 9d 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 rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
description: This skill should be used when the user mentions "Dockerfile", "docker image size", "container security", "multi-stage build", "distroless", "run as root", "docker layer caching", or is reviewing/optimizing Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
| `apt-get` with no cleanup | apt lists/caches bloat the layer | `--no-install-recommends` + `rm -rf /var/lib/apt/lists/*` in the same `RUN` | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dockerfile Smells and Hardening
Purpose
A consistent set of Dockerfile anti-patterns and their fixes, so container reviews produce smaller, safer, cache-friendly images the same way every time. This is container-build domain knowledge, the specific smells and the reasons they matter, not generic Docker syntax.
Smell catalog
| Smell | Why it hurts | Fix |
|---|---|---|
Runs as root (no USER) |
container escape = host root; violates PSS/most policies | add USER <uid> (numeric, non-root) |
latest / unpinned base tag |
non-reproducible; silent base drift; supply-chain risk | pin FROM img@sha256:<digest> |
| Single-stage build | ships compilers, headers, build deps in runtime image | multi-stage: build → slim runtime |
COPY . . before dep install |
any source edit busts the dependency cache layer | copy manifests, install, then copy source |
| Secrets baked in a layer | recoverable from image history forever | RUN --mount=type=secret; never ENV TOKEN= |
apt-get with no cleanup |
apt lists/caches bloat the layer | --no-install-recommends + rm -rf /var/lib/apt/lists/* in the same RUN |
Missing .dockerignore |
huge context; .git/secrets sent to daemon |
add .dockerignore |
No HEALTHCHECK |
orchestrator can't detect a wedged process | add HEALTHCHECK where the app exposes a check |
ADD for local files / remote URLs |
silent auto-extract, unverified downloads | use COPY; fetch with verified checksums |
Many chained RUN layers |
extra layers, larger image | combine related commands, order by volatility |
Hardening principles (apply in order)
- Least privilege at runtime: non-root numeric
USER, drop capabilities, read-only root filesystem where possible. - Minimal surface: distroless or
-slimruntime base; install only what runs in production. - Reproducibility: pin base image by digest; pin package versions where feasible.
- Cache efficiency: order layers least-volatile → most-volatile (base, then deps, then source).
- No secrets in layers: build secrets via BuildKit mounts; runtime secrets via the orchestrator, never
ENV/ARGbake-in.
What ships with it
2 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.
- 9d ago First seen · 43 lines · 76 tokens per session scan B f73db594f757
dockerfile-smells is a skill published in the GitHub repository sigistry/marketplace (3 stars, last pushed 5d ago), licensed MIT. It adds 76 tokens to every session and 812 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B 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
infra-standards
Infrastructure, container, and CI/CD discipline — IaC, Dockerfiles and compose files, CI pipelines, platform deploy config, env/secrets handling. INVOKE PROACTIVELY when creating or editing any such file (.tf, .bicep, Dockerfile, docker-compose, .github/workflows/, vercel.json) — even when nobody says "infra". Not for…
ci-cd-pipeline
Use near the end of a project to generate CI and make the app deploy-ready. Produces a polyglot GitHub Actions workflow (lint, typecheck, test, build) and multi-stage Dockerfiles. The finish line is CI-green and container-ready, not an actual deploy.
docker-dev-environment
Use when setting up local development services or running the project locally. Establishes the "stateful services in Docker, app runs native" pattern with Postgres, Redis, MinIO, and Mailpit.
helm
Helm chart authoring, templating, and release management for Kubernetes: charts, values, templating functions, repositories, dependencies, and lifecycle operations.
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…