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/hamzafarooq/claude-code-starter/dockerfile-generatornpx skills add hamzafarooq/claude-code-starter --skill dockerfile-generatorgit clone --depth 1 https://github.com/hamzafarooq/claude-code-starterWrote 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/hamzafarooq/claude-code-starter/dockerfile-generator)<a href="https://agentmods.dev/skills/hamzafarooq/claude-code-starter/dockerfile-generator"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/dockerfile-generator.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.00050 | $0.00348 |
| Opus 5 | $0.00025 | $0.00174 |
| Sonnet 5 | $0.00010 | $0.00070 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
dockerfile-generator scanned grade A with 0 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 3d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Ask the user:
- "What language and framework? (e.g. Python/FastAPI, Node/Next.js, Go)"
- "What platform are you deploying to? (Fly.io, Railway, Cloud Run, self-hosted)"
- "Any environment variables the app needs at runtime?"
Then produce:
Dockerfile
# [explanation of each stage]
What this Dockerfile does:
- Base image choice and why
- Multi-stage build explanation (if used)
- How dependencies are cached for fast rebuilds
- Non-root user setup (security)
- Health check configuration
Platform config (if applicable)
fly.toml (for Fly.io):
# minimal fly.toml
Commands to deploy:
# step-by-step deployment commands
.dockerignore
node_modules/
.env
.env.local
*.log
.git
Security checklist:
- App runs as non-root user
- No secrets in the image layers
- Only production dependencies installed
- Health check defined
- Image size under [target — e.g. 200MB for Node, 100MB for Python Alpine]
Flag any environment variable that looks like a secret — confirm it's being passed at runtime, not baked into the image.
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.
- 3d ago First seen · 63 lines · 50 tokens per session scan A 1f13e2a590fe
dockerfile-generator is a skill published in the GitHub repository hamzafarooq/claude-code-starter (138 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 348 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…
reproduce-issue
The single skill for reproducing an nx issue. Given a GitHub issue number (human entry) OR explicit repro parameters (agent entry), it runs the reproduction ENTIRELY inside an isolated Docker sandbox — gVisor on Linux, the Docker VM on macOS — so the untrusted repro's install scripts and commands never execute on the…
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
windows-builder
Build Windows images with Packer using WinRM communicator and PowerShell provisioners. Use when creating Windows AMIs, Azure images, or VMware templates.
self-host-studio
Install and self-host deco Studio (the open-source control plane) on the user's own infrastructure. Use when the user wants to install, run, self-host, or deploy Studio locally (Docker, Rancher Desktop, kind, minikube) or on Kubernetes (managed or self-managed), or asks to "install Studio", "self-host decocms"…
cluster-manage
Manage Kurtosis cluster settings. Switch between Docker and Kubernetes backends, list available clusters, and configure which cluster Kurtosis uses. Use when you need to change where Kurtosis runs enclaves.