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/slicervm/agent-skills/use-dockernpx skills add slicervm/agent-skills --skill use-dockergit clone --depth 1 https://github.com/slicervm/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/slicervm/agent-skills/use-docker)<a href="https://agentmods.dev/skills/slicervm/agent-skills/use-docker"><img src="https://agentmods.dev/badge/skills/slicervm/agent-skills/use-docker.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.00076 | $0.00675 |
| Opus 5 | $0.00038 | $0.00338 |
| Sonnet 5 | $0.00015 | $0.00135 |
| Haiku 4.5 | $0.00008 | $0.00068 |
Grade D, and why
use-docker scanned grade D with 3 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
curl -LSs https://get.docker.com | sudo bash Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -LSs https://get.docker.com | sudo bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -LSs https://get.docker.com | sudo bash How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use Docker Engine
Installation policy
Prefer Docker's official installer so that Docker Engine comes from Docker's repository and does not lag behind upstream releases.
- Never substitute
apt install docker.io,apt install docker-compose, or similar distribution packages when the official installer supports the machine. Ubuntu and Debian packages can be significantly behind. - Use APT-packaged Docker only as a last resort when the official installer is genuinely incompatible or unavailable, and state why the fallback is necessary.
- Do not reinstall Docker when a suitable working installation already exists.
Install on Ubuntu, Debian, or a Slicer VM
Run the official installer, add the standard ubuntu user to the Docker
group, and ensure the daemon is enabled and running:
curl -LSs https://get.docker.com | sudo bash
sudo usermod -aG docker ubuntu
sudo systemctl enable --now docker
Membership of the docker group grants root-equivalent access. Add only the
intended trusted user.
For a non-Slicer machine whose login user is not ubuntu, replace ubuntu
with that non-root login name. Do not add root to the group.
Use the new group membership
An existing shell does not automatically gain a newly added supplementary
group. Reconnect to the machine before running docker directly, or use sg
for commands that must run immediately:
sg docker -c 'docker version'
sg docker -c 'docker run --rm hello-world'
In longer-lived automation, keep the command inside sg docker -c '...' until
the session has been recreated. Do not weaken the socket permissions with
chmod 666 /var/run/docker.sock.
Build, run, and compose
After reconnecting, use Docker normally:
docker build -t myapp:latest .
docker run --rm -p 8080:8080 myapp:latest
docker compose up -d
Before assuming an old standalone docker-compose binary is required, try
the current Compose plugin:
docker compose version
Diagnose failures
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 · 87 lines · 76 tokens per session scan D d425390786b6
use-docker is a skill published in the GitHub repository slicervm/agent-skills (5 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 675 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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.