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/glincker/claude-code-marketplace/docker-wizardnpx skills add glincker/claude-code-marketplace --skill docker-wizardgit clone --depth 1 https://github.com/glincker/claude-code-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/glincker/claude-code-marketplace/docker-wizard)<a href="https://agentmods.dev/skills/glincker/claude-code-marketplace/docker-wizard"><img src="https://agentmods.dev/badge/skills/glincker/claude-code-marketplace/docker-wizard.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.00019 | $0.01583 |
| Opus 5 | $0.00010 | $0.00792 |
| Sonnet 5 | $0.00004 | $0.00317 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade A, and why
docker-wizard 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Wizard
Generate production-ready Dockerfiles and docker-compose.yml files by analyzing your project. Follows best practices, optimizes image size, and includes security hardening.
What This Skill Does
- Auto-detects project type and dependencies
- Generates multi-stage builds for smaller images
- Applies security best practices (non-root user, minimal base images)
- Creates docker-compose.yml for multi-service setups
- Includes development and production configurations
- Optimizes layer caching for faster builds
Instructions
Phase 1: Project Analysis
-
Detect project type:
Use Glob to find: - package.json → Node.js - requirements.txt/pyproject.toml → Python - go.mod → Go - Cargo.toml → Rust - pom.xml/build.gradle → Java -
Analyze dependencies:
Use Read to examine: - Runtime dependencies - Build dependencies - Environment requirements - Port requirements
Phase 2: Dockerfile Generation
Generate optimized multi-stage Dockerfile:
# Example for Node.js
# Stage 1: Dependencies
FROM node:20-alpine AS deps
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
# Stage 2: Build
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build
# Stage 3: Production
FROM node:20-alpine AS runner
WORKDIR /app
# Security: Run as non-root user
RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs
COPY --from=deps --chown=nextjs:nodejs /app/node_modules ./node_modules
COPY --from=builder --chown=nextjs:nodejs /app/dist ./dist
USER nextjs
EXPOSE 3000
CMD ["node", "dist/index.js"]
Best practices applied:
- Multi-stage builds (reduce image size by 70%)
- Alpine base images (minimal attack surface)
- Non-root user (security)
- Optimized layer caching
- .dockerignore generation
Phase 3: Docker Compose Generation
Create docker-compose.yml for multi-service setups:
version: '3.9'
services:
app:
build:
context: .
dockerfile: Dockerfile
ports:
- "3000:3000"
environment:
- NODE_ENV=production
- DATABASE_URL=postgresql://user:pass@db:5432/myapp
depends_on:
db:
condition: service_healthy
restart: unless-stopped
db:
image: postgres:16-alpine
environment:
- POSTGRES_USER=user
- POSTGRES_PASSWORD=pass
- POSTGRES_DB=myapp
volumes:
- postgres_data:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U user"]
interval: 10s
timeout: 5s
retries: 5
restart: unless-stopped
redis:
image: redis:7-alpine
ports:
- "6379:6379"
restart: unless-stopped
volumes:
postgres_data:
What ships with it
1 file 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.
- 5d ago First seen · 269 lines · 19 tokens per session scan A fb26bbe56d4f
docker-wizard is a skill published in the GitHub repository glincker/claude-code-marketplace (36 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,583 once invoked, about $0.0001 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
docker-docs
Comprehensive Docker 28.x reference covering all features: installation, Dockerfile instructions, multi-stage builds, Docker Compose, networking, volumes, CLI commands, image management, registries, security best practices, CI/CD integration, debugging, and Kubernetes migration. Use whenever the user mentions Docker…
docker-essentials
Create and optimize Dockerfiles, docker-compose configurations, and container workflows. Use when containerizing applications, setting up development environments, or optimizing Docker builds.
docker-agent
Write optimized Dockerfiles, docker-compose configs, and debug container issues. Use when containerizing an app, fixing a broken container, or designing a multi-service local environment.
docker-management
Docker container lifecycle management, Dockerfile authoring, and debugging.
k8s-yaml-prod
Production-grade Kubernetes YAML standards calibrated to this repo's actual conventions (Jenkins $VARS templating, Harbor imagePullSecrets, tcpSocket probes, multi-cluster overlays under devops/ /). Use BEFORE writing or modifying any K8s YAML for production — Deployment / StatefulSet / DaemonSet / Service / Ingress /…
k8s-cleanup-stuck
Diagnose and safely clean up stuck Kubernetes resources — Terminating CR/namespace, RBAC residuals after operator removal, dead admission webhooks silently blocking API. Use when user mentions 卡 Terminating, kubectl delete 卡住, 卸载残留, RBAC forbidden, webhook 拦 API, namespace 删不掉, finalizer 卡, operator 没清干净…