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 skills add thienanblog/awesome-ai-agent-skills --skill docker-local-devgit clone --depth 1 https://github.com/thienanblog/awesome-ai-agent-skillsWrote 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/thienanblog/awesome-ai-agent-skills/docker-local-dev)<a href="https://agentmods.dev/skills/thienanblog/awesome-ai-agent-skills/docker-local-dev"><img src="https://agentmods.dev/badge/skills/thienanblog/awesome-ai-agent-skills/docker-local-dev/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/thienanblog/awesome-ai-agent-skills/docker-local-dev"><img src="https://agentmods.dev/badge/skills/thienanblog/awesome-ai-agent-skills/docker-local-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 116 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.1 | $0.00072 | $0.01861 |
| Opus 5 | $0.00036 | $0.00931 |
| Sonnet 5 | $0.00014 | $0.00372 |
| Haiku 4.5 | $0.00007 | $0.00186 |
Grade A, and why
docker-local-dev 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 12d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Local Development
Run this skill in the main conversation. Do not spawn subagents, agent teams, or delegated parallel workers unless the user explicitly approves the proposed count and scope after being told that doing so can increase usage. Ask again before expanding an approved scope.
Guardrails
- Design for local development. Keep production images, secrets, deployment, certificates, and runtime topology separate.
- Inspect before asking questions or proposing services. Treat detection as evidence, not authority.
- Ask only about unresolved choices that materially change the result. Group related questions and recommend a default; do not force a fixed questionnaire.
- Preserve existing Docker files and unrelated working-tree changes. Show a semantic diff before replacing or materially restructuring a working stack. Never commit, reset, delete volumes, run migrations or seeds, or overwrite files unless the user authorized that action.
- Generate only services the project uses or the user explicitly requests. A database is not mandatory when the project uses SQLite, a host service, or an external database.
- Prefer direct foreground commands and one concern per service. Add Supervisor or PM2 only when the project already requires it or production-parity testing justifies it.
- Prefer a stable top-level Compose
name:and role-based service names. Do not setcontainer_nameby default because it prevents service scaling and creates cross-project collisions. - Select images by project constraints, team or production compatibility, trusted publisher, supported version, and architecture. Treat an already-downloaded image only as a tie-breaker. Avoid floating
latesttags in generated files. - Publish only ports needed by the host. Bind local-only ports to
127.0.0.1by default; keep databases, caches, SMTP, PHP-FPM, and internal APIs unexposed when possible. - Keep secrets out of committed files, generated documentation, command output, and frontend or proxy containers. Generate an ignored local env file plus a safe example when configuration is needed.
What ships with it
36 files 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.
- assets/templates/docker-compose/base.yml 325 B
- assets/templates/docker-compose/node.yml 3.8 KB
- assets/templates/docker-compose/php-drupal.yml 3.0 KB
- assets/templates/docker-compose/php-joomla.yml 2.6 KB
- assets/templates/docker-compose/php-laravel.yml 2.0 KB
- assets/templates/docker-compose/php-wordpress.yml 3.7 KB
- assets/templates/docker-compose/python.yml 4.3 KB
- assets/templates/dockerfile/node.dockerfile 1.0 KB
- assets/templates/dockerfile/php-drupal.dockerfile 2.0 KB
- assets/templates/dockerfile/php-joomla.dockerfile 1.9 KB
- assets/templates/dockerfile/php-laravel.dockerfile 2.1 KB
- assets/templates/dockerfile/php-wordpress.dockerfile 2.0 KB
- assets/templates/dockerfile/python-django.dockerfile 1.4 KB
- assets/templates/dockerfile/python-fastapi.dockerfile 1.3 KB
- assets/templates/docs/COMMANDS.md.template 836 B
- assets/templates/docs/USAGE.md.template 2.0 KB
- assets/templates/nginx/drupal.conf 2.7 KB
- assets/templates/nginx/joomla.conf 2.2 KB
- assets/templates/nginx/laravel.conf 567 B
- assets/templates/nginx/node-proxy.conf 2.6 KB
- assets/templates/nginx/python-wsgi.conf 2.8 KB
- assets/templates/nginx/wordpress.conf 703 B
- assets/templates/wordpress/wp-config-docker.php 2.6 KB
- references/cms-configuration-guide.md 3.9 KB
- references/health-check-patterns.md 4.2 KB
- references/merge-backup-strategy.md 3.0 KB
- references/networking-ports-guide.md 5.7 KB
- references/service-configuration-guide.md 9.1 KB
- references/tech-stack-detection.md 4.3 KB
- scripts/db-test.sh 5.0 KB runs code
- scripts/detect-images.sh 2.0 KB runs code
- scripts/detect-network.sh 2.9 KB runs code
- scripts/detect-stack.sh 13 KB runs code
- scripts/health-check.sh 2.8 KB runs code
- scripts/port-check.sh 5.0 KB runs code
- scripts/scan-host-ports.mjs 18 KB runs code
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.
- 12d ago First seen · 186 lines · 72 tokens per session scan A 9b60314ed370
docker-local-dev is a skill published in the GitHub repository thienanblog/awesome-ai-agent-skills (65 stars, last pushed 14d ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,861 once invoked, about $0.0004 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…
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.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.