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/cookiemonsterdev/agents-skills/docker-docsnpx skills add cookieMonsterDev/agents-skills --skill docker-docsgit clone --depth 1 https://github.com/cookieMonsterDev/agents-skillsWhat 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.00095 | $0.01361 |
| Opus 5 | $0.00048 | $0.00681 |
| Sonnet 5 | $0.00019 | $0.00272 |
| Haiku 4.5 | $0.00010 | $0.00136 |
Grade A, and why
docker-docs 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker questions are easy to answer from stale memory or pre-Compose-v2 patterns. Use this skill to ground answers in the official Docker documentation and return the closest authoritative page instead of generic container advice.
When to Use
Use this skill when the request is about:
- Docker concepts, architecture, containers, images, and the Docker Engine daemon
- Installing or configuring Docker Engine, Docker Desktop, or Docker Compose
- Dockerfile syntax, image builds, multi-stage builds, and Buildx
- Compose file format,
docker composeworkflows, profiles, and overrides - Container lifecycle: run, exec, logs, inspect, stop, restart, and resource limits
- Images: pull, push, tag, prune, and registry authentication
- Networking: bridge, host, overlay, published ports, and DNS
- Volumes, bind mounts, tmpfs, and storage drivers
- Docker Engine API, SDKs, and API version negotiation
- Swarm mode: services, stacks, secrets, configs, and nodes
- Security: rootless mode, content trust, Scout, and hardened images
- Troubleshooting daemon, build, networking, or registry errors
Do not use this skill for:
- Kubernetes cluster operations or
kubectlusage. Usekubernetes-docsinstead. - AWS CLI commands for ECS, ECR, or Fargate. Use
aws-cli-docsinstead. - Third-party orchestrators (Nomad, Podman docs) unless the question is about Docker compatibility or migration covered in Docker docs.
- Application framework questions unrelated to Docker (NestJS, Express, etc.) unless the user is asking about containerizing that stack per Docker docs.
Workflow
1. Classify the request
Decide which bucket the question belongs to before searching:
- Getting started and core concepts
- Installation and platform setup (Engine, Desktop, Compose)
- Dockerfile and image builds
- Compose file format and multi-container apps
- CLI reference (docker, compose, buildx)
- Networking, storage, and runtime configuration
- Registries, distribution, and image security
- Engine API and SDKs
- Swarm and orchestration
- Security, rootless, and supply chain
- Troubleshooting and diagnostics
What ships with it
2 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.
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 · 113 lines · 95 tokens per session scan A dbe36afc9c6f
docker-docs is a skill published in the GitHub repository cookieMonsterDev/agents-skills (4 stars, last pushed 13d ago), licensed MIT. It adds 95 tokens to every session and 1,361 once invoked, about $0.0005 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.
Other skills, from other repositories
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).
wrangler
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over…
skillshare-devcontainer
Run CLI commands, tests, and debugging inside the skillshare devcontainer. Use this skill whenever you need to: execute skillshare CLI commands for verification, run Go tests (unit or integration), reproduce bugs, test new features, start the web UI, or perform any operation that requires a Linux environment. All CLI…
managing-astro-local-env
Manage local Airflow environment with Astro CLI (Docker and standalone modes). Use when the user wants to start, stop, or restart Airflow, view logs, query the Airflow API, troubleshoot, or fix environment issues. For project setup, see setting-up-astro-project.
aws-cloudformation-ecs
Provides AWS CloudFormation patterns for ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, CodeDeploy integration, ALB integration, service discovery, monitoring, logging, template structure, parameters, outputs, and cross-stack references. Use when creating ECS…
aws-cloudformation-task-ecs-deploy-gh
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…