docker-setup

A project setup workflow that detects the programming stack and generates Docker files for building and running it. Docker packages an application and its runtime needs into repeatable containers.

In plain words
What is it for?
Creating a Dockerfile, Docker Compose configuration, and .dockerignore for projects using stacks such as Node.js, Python, Go, Rust, .NET, Ruby, PHP, or Elixir.
Why use it?
It removes much of the manual work of choosing base images, build steps, runtime dependencies, ports, services, and environment settings. It also prepares separate development and production configurations.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/viknesh20-20/claude-code-tool-kit/docker-setup
Any agent
npx skills add viknesh20-20/claude-code-tool-kit --skill docker-setup
Clone the repo
git clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kit

Made for: Claude Code, Codex.

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 713 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00045 $0.00713
Opus 5 $0.00023 $0.00357
Sonnet 5 $0.00009 $0.00143
Haiku 4.5 $0.00005 $0.00071

Measured 2d ago against content hash 8affd943e4a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docker-setup 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 2d 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.

.claude/skills/docker-setup/SKILL.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Docker Setup Generator

Detect Stack

!ls package.json requirements.txt pyproject.toml go.mod Cargo.toml *.csproj Gemfile composer.json mix.exs 2>/dev/null !ls Dockerfile docker-compose* .dockerignore 2>/dev/null !cat package.json 2>/dev/null | grep -E '"(main|scripts)"' -A 5 | head -10


Generation Process

Step 1: Analyze Requirements

From project files, determine:

  • Base image (node:20-alpine, python:3.12-slim, golang:1.22, rust:1.75, etc.)
  • Build steps (install deps, compile, bundle)
  • Runtime dependencies (only what's needed to run, not to build)
  • Port(s) the application listens on
  • Required services (database, cache, message queue)
  • Environment variables needed

Step 2: Generate Dockerfile

Multi-stage build pattern:

# Stage 1: Dependencies
FROM base AS deps
COPY lock-file .
RUN install-command

# Stage 2: Build
FROM deps AS build
COPY source .
RUN build-command

# Stage 3: Production
FROM base-slim AS production
COPY --from=build /app/dist ./dist
CMD ["start-command"]

Best practices to include:

  • Use specific image tags, not latest
  • Use .dockerignore to minimize context
  • Copy lock files before source (layer caching)
  • Run as non-root user
  • Set HEALTHCHECK
  • Use multi-stage builds to minimize final image size
  • Set appropriate EXPOSE port
  • Use ENTRYPOINT + CMD pattern

Step 3: Generate docker-compose.yml

services:
  app:
    build: .
    ports: ["3000:3000"]
    environment: ...
    depends_on: ...
    volumes: ...  # for dev: mount source code
    healthcheck: ...

  # Add required services
  db:  # if database detected
  redis:  # if cache detected

Include:

  • Development overrides (volume mounts, hot reload)
  • Named volumes for persistent data
  • Network configuration
  • Health checks for all services
  • Environment variable references (not hardcoded values)

Step 4: Generate .dockerignore

node_modules/
.git/
dist/
build/
*.log
.env
.env.*

Step 5: Document

Add comments explaining:

  • Why each stage exists
  • How to build: docker build -t app .
  • How to run: docker compose up
  • How to access: http://localhost:PORT
  • How to run tests in Docker

Read the full file on GitHub · 106 lines

Changes

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.

  1. 2d ago First seen · 106 lines · 45 tokens per session scan A 8affd943e4a4

Subscribe to this mod's changes

docker-setup is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 713 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

interview

Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.

Hmbown/CodeWhale · 40 tokens

local-frontend-check

Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.

ascending-llc/jarvis-registry · 52 tokens

ppt-review

Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.

Orkas-AI/Orkas · 2 tokens

helmor-debug-operate

Operate, reproduce, and debug a running local Helmor desktop development build through the Tauri MCP bridge. Use when the user asks to use Tauri MCP, towery MCP, the local dev build, the Tauri webview, visual end-to-end validation, UI automation, screenshots, DOM/accessibility snapshots, IPC or log tracing…

dohooo/helmor · 117 tokens

autoprompt

Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.

Spielewoy/autoprompt-skill · 56 tokens