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 agentmods add skills/azure/containerization-assist/generate-dockerfilenpx skills add Azure/containerization-assist --skill generate-dockerfilegit clone --depth 1 https://github.com/Azure/containerization-assistWrote 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/azure/containerization-assist/generate-dockerfile)<a href="https://agentmods.dev/skills/azure/containerization-assist/generate-dockerfile"><img src="https://agentmods.dev/badge/skills/azure/containerization-assist/generate-dockerfile.svg" alt="Measured on agentmods" 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 | $0.00090 | $0.07443 |
| Opus 5 | $0.00045 | $0.03721 |
| Sonnet 5 | $0.00018 | $0.01489 |
| Haiku 4.5 | $0.00009 | $0.00744 |
Grade B, and why
generate-dockerfile 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 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
`apt-get update && apt-get install -y --no-install-recommends <pkgs> && rm -rf /var/lib/apt/lists/*`. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Has `curl`: `HEALTHCHECK CMD curl -fsS http://localhost:<port>/health || exit 1` How it starts
The opening of the file, as written. The whole thing — 505 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Dockerfile
Produce a production-quality, secure Dockerfile (or enhancement plan for an existing one) for a single module. The output is a complete Dockerfile that the user can write to disk — not a description of one.
Inputs
| Field | Required | Description |
|---|---|---|
modulePath |
yes | Absolute path of the module to containerize (one of the modules from analyze-repo). |
language |
yes | java | dotnet | javascript | typescript | python | go | rust | php | ruby. |
languageVersion |
recommended | E.g. 21, 8.0, 20, 3.11. Substituted into the base image tag. |
framework |
optional | E.g. spring-boot, express, next, django, flask, asp.net-core, gin. |
environment |
optional | production (default) or development. |
targetPlatform |
optional | linux/amd64 (default) or linux/arm64. |
detectedDependencies |
optional | Used to choose extra apt/apk packages (e.g. native modules). |
detectedEnvVars |
optional | List from analyze-repo. Used to add ENV instructions for config/database vars and to WARN about secret-classified ones (never bake secrets in). |
existingDockerfile |
optional | If a Dockerfile is already at <modulePath>/Dockerfile, read its content and follow the Enhancement path instead of the Generation path. |
Prerequisite: analyze-repo
This skill needs language, framework, detectedDependencies, and
detectedEnvVars from the analyze-repo skill. If you don't already
have that output for <modulePath> from earlier in this conversation,
follow the analyze-repo skill against <modulePath> first, then come
back.
Decision: generate or enhance?
- Check if
<modulePath>/Dockerfileexists. - If no → Generation path (Step G1–G4 below).
- If yes → read the file, run Dockerfile analysis (Step E1), then Enhancement path (Step E2–E4).
Generation path
G1 — Choose build strategy
Use multi-stage if any of these:
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 · 505 lines · 90 tokens per session scan B 70c5818aa210
generate-dockerfile is a skill published in the GitHub repository Azure/containerization-assist (41 stars, last pushed 14d ago), licensed MIT. It adds 90 tokens to every session and 7,443 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
toolset-design
Design and validate new MCP toolsets, tools, and tool changes. Use when planning a new toolset, adding tools to an existing toolset, reviewing a toolset PR, or deciding whether a new tool is warranted. Covers the full lifecycle: eval-first validation, tool design methodology, consolidation patterns, and review…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
nvca-values-customization
Customize NVCA Operator Helm chart values in the native monorepo. Use when modifying vendored defaults, changing stack-derived install values, adding deployment-time overrides, or updating scripts under deploy/helm/nvca-operator.
portainer-mcp-hygiene
How to drive the Portainer MCP server's tools correctly — both reading and mutating. Reading: project responses with select (JMESPath), where the heavy fields live (snapshots, status blocks, managed fields), how to handle non-JSON Docker/K8s proxy endpoints (container and pod logs, stats, exec), and how to interpret…
node-logs
Retrieve logs from a Kubernetes node — systemd units (journalctl) or files under /var/log. Use when you need node-level evidence: containerd, kubelet, kernel/OOM, or anything the pod's own log cannot show. Three access paths in order: hostscript (SSH), nodescript (debug pod), and localscript against the kubelet log…