Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/kok-o/contextos-agentsnpx agentmods add skills/kok-o/contextos-agents/dockerWrote 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/kok-o/contextos-agents/docker)<a href="https://agentmods.dev/skills/kok-o/contextos-agents/docker"><img src="https://agentmods.dev/badge/skills/kok-o/contextos-agents/docker/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/kok-o/contextos-agents/docker"><img src="https://agentmods.dev/badge/skills/kok-o/contextos-agents/docker.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.01510 |
| Opus 5.5 | $0.00009 | $0.00604 |
| Sonnet 5.5 | $0.00005 | $0.00302 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
docker scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
CMD wget --no-verbose --tries=1 --spider http://127.0.0.1:3000/api/health || exit 1 How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker
Overview
Containerization, Dockerfile architecture, multi-stage compilation, security hardening, and container orchestration for production workloads.
When to Use
Activate when creating or optimizing Dockerfiles, docker-compose configurations, container security audits, CI/CD container build stages, or production container deployments.
Rules & Patterns
Negative Constraints (What NOT to Do)
- NEVER run containers as
rootin production: Always create and switch to an unprivileged non-root user (e.g.USER nodeorUSER nonroot). - NEVER use the
latesttag: Always pin base images to specific immutable version digests or explicit minor tags (e.g.node:22-alpine3.20orpython:3.12-slim-bookworm). - NEVER copy source code before dependency manifests: Always copy package manifests (
package.json,pnpm-lock.yaml,pyproject.toml) and install dependencies first to maximize Docker layer cache hits. - NEVER bake secrets, API keys, or
.envfiles into image layers: Pass secrets via build-time secret mounts (--mount=type=secret) or runtime environment variables injected by the orchestrator. - NEVER include build tools or devDependencies in the final runner image: Always use multi-stage builds to discard compilers, package managers, and temporary build caches from production images.
- NEVER run without a
.dockerignorefile: Always exclude.git,node_modules,.env*, and build outputs from the Docker build context.
Pattern 1: Node.js / Next.js Standalone Multi-Stage Dockerfile
Optimized multi-stage build producing minimal production images (<120MB) with non-root security:
# ── Stage 1: Dependencies ─────────────────────────────────────────────
FROM node:22-alpine3.20 AS deps
RUN apk add --no-cache libc6-compat
WORKDIR /app
COPY package.json pnpm-lock.yaml* package-lock.json* yarn.lock* ./
RUN \
if [ -f pnpm-lock.yaml ]; then corepack enable pnpm && pnpm i --frozen-lockfile; \
elif [ -f package-lock.json ]; then npm ci; \
else yarn --frozen-lockfile; \
fi
# ── Stage 2: Builder ──────────────────────────────────────────────────
FROM node:22-alpine3.20 AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .
ENV NEXT_TELEMETRY_DISABLED=1
ENV NODE_ENV=production
RUN npm run build
# ── Stage 3: Production Runner ────────────────────────────────────────
FROM node:22-alpine3.20 AS runner
WORKDIR /app
ENV NODE_ENV=production
ENV PORT=3000
ENV HOSTNAME="0.0.0.0"
RUN addgroup --system --gid 1001 nodejs && \
adduser --system --uid 1001 nextjs
# Copy standalone output and static assets
COPY --from=builder /app/public ./public
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
USER nextjs
EXPOSE 3000
HEALTHCHECK --interval=30s --timeout=5s --start-period=5s --retries=3 \
CMD wget --no-verbose --tries=1 --spider http://127.0.0.1:3000/api/health || exit 1
CMD ["node", "server.js"]
What ships with it
4 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.
- today First seen · 170 lines · 23 tokens per session scan A 0032f0380baf
docker is a skill published in the GitHub repository kok-o/contextos-agents (10 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 1,510 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-25.
Other skills, from other repositories
harness
To build an AI harness: run, observe, validate, automate repeated work faster — CLI/MCP actions, devcontainers, skills, subagents, hooks, pipelines, automations.
kubestellar-console
Multi-cluster Kubernetes dashboard with AI-powered operations via MCP server and 10+ built-in agent skills.
kubernetes-expert
Expert Kubernetes: workloads, services, config, probes, resources, and troubleshooting. Trigger keywords: Kubernetes, k8s, Deployment, StatefulSet, Service, Pod, ConfigMap, Secret, Ingress, liveness, readiness, probe, requests, limits, HPA, kubectl, Helm, CrashLoopBackOff, ImagePullBackOff, OOMKilled. Use for writing…
docker-expert
Expert Docker: Dockerfiles, multi-stage builds, image size/cache optimization, Compose, and container best practices. Trigger keywords: Docker, Dockerfile, container, image, multi-stage, layer cache, docker-compose, .dockerignore, entrypoint, distroless, non-root, healthcheck, build context. Use for writing/optimizing…
ai-engineering-toolkit
6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.
hosted-agents-v2-py
Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition. Use when creating container-based agents in Azure AI Foundry.