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/wrsmith108/claude-code-docker-skill/dockernpx skills add wrsmith108/claude-code-docker-skill --skill dockergit clone --depth 1 https://github.com/wrsmith108/claude-code-docker-skillWhat 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.00056 | $0.02029 |
| Opus 5 | $0.00028 | $0.01014 |
| Sonnet 5 | $0.00011 | $0.00406 |
| Haiku 4.5 | $0.00006 | $0.00203 |
Grade A, and why
docker scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:3000 > /dev/null && echo "Server running" || echo "Server not running" How it starts
The opening of the file, as written. The whole thing — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Development Skill
Execute all package installations and code execution inside Docker containers. This keeps the host machine clean and ensures consistent environments across projects.
Core Principle
NEVER run npm, node, npx, or project scripts directly on the host machine.
Instead, use docker exec or ensure the container is running the dev server.
Pre-Flight Check (MANDATORY)
Before running ANY npm/node command, Claude Code MUST verify the container is running.
Run this check first:
docker ps --filter "name=<project-name>" --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"
Expected output:
NAMES STATUS PORTS
<project-name>-dev-1 Up X minutes 0.0.0.0:3000->3000/tcp
If container is NOT running:
# Navigate to project root first
cd /path/to/your/project
# Start container
docker-compose --profile dev up dev -d
# Verify it started
docker ps --filter "name=<project-name>"
If container shows "Exited":
# Check why it exited
docker logs <project-name>-dev-1 --tail 20
# Remove and restart
docker-compose --profile dev down
docker-compose --profile dev up dev -d
Quick Reference
Check Container Status
# List running containers for current project
docker ps --filter "name=<project-name>"
# Check container logs
docker logs <project-name>-dev-1 --tail 50
# Check if dev server is responding
curl -s http://localhost:3000 > /dev/null && echo "Server running" || echo "Server not running"
Start/Stop Containers
# Start development container (from project root)
docker-compose --profile dev up dev -d
# Stop container
docker-compose --profile dev down
# Restart container
docker-compose --profile dev restart dev
# Rebuild after Dockerfile changes
docker-compose --profile dev up dev -d --build
Execute Commands Inside Container
# Install a package
docker exec -it <project-name>-dev-1 npm install <package-name>
# Install dev dependency
docker exec -it <project-name>-dev-1 npm install -D <package-name>
# Run tests
docker exec -it <project-name>-dev-1 npm test
# Run type checking
docker exec -it <project-name>-dev-1 npm run typecheck
# Run linting
docker exec -it <project-name>-dev-1 npm run lint
# Run build
docker exec -it <project-name>-dev-1 npm run build
# Open shell inside container
docker exec -it <project-name>-dev-1 /bin/sh
# Run any arbitrary command
docker exec -it <project-name>-dev-1 <command>
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.
- 2d ago First seen · 315 lines · 56 tokens per session scan A 3a35aa9eade1
docker is a skill published in the GitHub repository wrsmith108/claude-code-docker-skill (4 stars, last pushed 8mo ago), licensed MIT. It adds 56 tokens to every session and 2,029 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
anti-slop
· Audit AI-generated code slop: hallucinated APIs, over-abstraction, duplicate code, test theater, noisy comments. Triggers: 'slop', 'AI-generated code', 'cleanup', 'overengineered'. Not for prose (use anti-ai-prose).
code-review
· Review code for correctness: bugs, edge cases, races, leaks, regressions. Triggers: 'review', 'code review', 'find bugs', 'check this', 'spot check', 'sanity check'. Not for style/slop (anti-slop) or vulnerabilities (security-audit).
kubernetes
· Write/review Kubernetes manifests, Helm, Kustomize, Gateway API, ArgoCD, sealed secrets. Triggers: 'kubernetes', 'k8s', 'helm', 'kubectl', 'deployment', 'pod', 'ingress', 'gateway'.
ai-ml
· Build/review AI apps: LLMs, RAG, embeddings, agents, evals, local inference. Triggers: 'llm', 'rag', 'embedding', 'openai sdk', 'agent loop', 'fine-tune', 'ollama', 'vllm'. Not for MCP (use mcp).
ansible
· Write/review Ansible playbooks, roles, inventories, Vault, Molecule, AWX/AAP. Triggers: 'ansible', 'playbook', 'role', 'inventory', 'groupvars', 'ansible-lint'.
ci-cd
· Write/review CI/CD for GitHub Actions, GitLab, Forgejo/Gitea, Woodpecker. Triggers: 'ci/cd', 'pipeline', 'github actions', 'gitlab ci', 'runner', 'renovate', 'trivy'. Not for git workflows (use git).