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 AmariahAK/atlarix-skills --skill dockergit clone --depth 1 https://github.com/AmariahAK/atlarix-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/amariahak/atlarix-skills/docker)<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/docker"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/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.1 | $0.00002 | $0.00399 |
| Opus 5 | $0.00001 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
Docker Patterns 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 4d 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 Patterns
When to use this skill
Use this skill when containerizing an app or debugging container behavior (build failures, missing deps, runtime env differences).
Core patterns
Minimal images
Prefer:
- multi-stage builds
- smallest base image that fits requirements
Avoid:
- copying the entire repo when you can copy only what’s needed
Deterministic builds
- pin base images when possible
- avoid
latestin production - keep build context small with
.dockerignore
Runtime vs build dependencies
Separate:
- build tooling (compilers, dev deps)
- runtime deps only in final stage
Compose for local dev
Use docker-compose.yml for:
- local DB/cache
- multi-service integration
Debugging containers
Checklist:
- confirm env vars inside container
- confirm file paths and working directory
- confirm ports exposed and mapped
- inspect logs
Atlarix tool notes
- Explore: inspect
Dockerfile,docker-compose.yml, and entrypoint scripts. - Build: run docker build/run commands and capture output.
- Debug: reproduce locally with the smallest container steps; check logs first.
- Review: verify secrets aren’t baked into images; check for overly-permissive settings.
Common mistakes to avoid
- Using
latesttags in production - Leaking secrets via
ENVor copied files - Forgetting
.dockerignore - Shipping dev tools in runtime image
Mini-checklist
- Multi-stage build used when appropriate
.dockerignorepresent- Secrets handled safely
- Logs + ports verified
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.
- 4d ago First seen · 65 lines · 2 tokens per session scan A c9fa3734f0a5
Docker Patterns is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 2 tokens to every session and 399 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-09-03.
Other skills, from other repositories
ecspresso
ECS deployment tool - deploy, manage, and troubleshoot ECS services.
coolify
Use when self-hosting apps and databases with Coolify on a VPS you own — install, first-admin lockdown, Git-to-deploy (Nixpacks/Dockerfile/compose), managed Postgres/Redis, scheduled S3 backups, domains + auto-SSL. NOT a PaaS someone else runs (that is railway), NOT sizing/hardening the box (that is hetzner), NOT…
docker
Use when authoring or auditing a Dockerfile, shrinking a bloated image, hardening a container that runs as root, picking a base image, or wiring a Compose dev loop with hot reload. NOT CI builds or deploy-to-host (that is deployment), NOT k8s autoscaling (that is scaling), NOT app-level injection or secrets-in-code…
container-manager-kubernetes-operations
Full operational Kubernetes surface via the container-manager-mcp MCP server — workloads (pods/rollouts/StatefulSets/DaemonSets/ReplicaSets/Jobs/CronJobs), config (ConfigMaps/Secrets/Namespaces/CRDs/patch), networking (Ingress/native Services/NetworkPolicy/DNS), storage (PV/PVC/StorageClass/snapshots/CSI), RBAC…
container-manager-config-walkthrough
End-user setup guide for the container-manager-mcp MCP server — choosing CONTAINERMANAGERTYPE (docker/podman/kubernetes/multi), wiring .env / mcpconfig toggles, connecting remote Docker/Podman hosts via the tunnel-manager inventory versus remote Kubernetes clusters via kubeconfig contexts, and a first-run verification…
container-manager-multi-context
Operate several container backends and contexts at once — Kubernetes, Docker, Podman, and Swarm — via the container-manager-mcp MCP server's cmmulticontext tool, with per-call backend/context selection and parallel fan-out across a configured pool of contexts. Use when the agent must compare, migrate between, or…