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/gebruder/wirken/dockernpx skills add gebruder/wirken --skill dockergit clone --depth 1 https://github.com/gebruder/wirkenWrote 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/gebruder/wirken/docker)<a href="https://agentmods.dev/skills/gebruder/wirken/docker"><img src="https://agentmods.dev/badge/skills/gebruder/wirken/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.00005 | $0.00293 |
| Opus 5 | $0.00003 | $0.00147 |
| Sonnet 5 | $0.00001 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
docker 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 3d 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.
What it actually says
Docker
Manage Docker containers and images.
Containers
- List running:
docker ps - List all:
docker ps -a - Run:
docker run -d --name <name> <image> - Stop:
docker stop <name> - Remove:
docker rm <name> - Logs:
docker logs <name> --tail 50 - Exec into:
docker exec -it <name> sh - Inspect:
docker inspect <name> | jq '.[0].State'
Images
- List:
docker images - Pull:
docker pull <image> - Build:
docker build -t <tag> . - Remove:
docker rmi <image>
Compose
- Start:
docker compose up -d - Stop:
docker compose down - Logs:
docker compose logs --tail 50 - Status:
docker compose ps
Cleanup
- Remove stopped containers:
docker container prune -f - Remove unused images:
docker image prune -f - Disk usage:
docker system df
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.
- 3d ago First seen · 52 lines · 5 tokens per session scan A f3258671cca8
docker is a skill published in the GitHub repository gebruder/wirken (169 stars, last pushed 4d ago), licensed MIT. It adds 5 tokens to every session and 293 once invoked, about $0.0000 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
run-local
Bring the full Nexus Gateway local stack up from a clean clone — PostgreSQL + Valkey + NATS via docker-compose, four Go services (Hub / Control Plane / AI Gateway / Compliance Proxy), and the Control Plane UI (Vite). Encodes every gotcha a first-time OSS contributor hits so the model can drive the full bring-up…
carto
The catalog lives in stoa-infra (private repo), NOT in the public stoa repo.
helm-update
Apply helm chart updates for Bifrost. Detects config.schema.json changes since the last helm release, applies user-requested changes, updates values.yaml / values.schema.json / helpers.tpl, bumps Chart.yaml version, updates helm README (Latest Version + Upcoming section), creates a docs MDX changelog, and updates…
plano-deployment-security
Apply Plano deployment and production security practices. Use for Docker networking, state storage choices, readiness checks, and environment-based secret handling.
defenseclaw-ops
Manage DefenseClaw enterprise security - scan components, manage tool permissions, view alerts, configure guardrails.
railway-volume-to-docker
Sync runtime data from a Railway deployment into local Docker for realistic testing. Use when the user asks to copy Railway data, clone production state locally, or test with real usage/session/config data.