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 christopherlouet/claude-base --skill ops-dockergit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/ops-docker)<a href="https://agentmods.dev/skills/christopherlouet/claude-base/ops-docker"><img src="https://agentmods.dev/badge/skills/christopherlouet/claude-base/ops-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.00025 | $0.00647 |
| Opus 5 | $0.00013 | $0.00324 |
| Sonnet 5 | $0.00005 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
ops-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 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Containerization (pointer)
Dockerfile syntax, Compose schema and image-publish flows drift on each release and are canonical at:
- Docker official — docs.docker.com (Engine + Compose + Buildx)
- Dockerfile best practices — docs.docker.com/develop/develop-images/dockerfile_best-practices
- Snyk Container Security — snyk.io/learn/container-security (vulnerability scanning, base-image hardening)
- Hadolint — github.com/hadolint/hadolint (Dockerfile linter, CI-integrable)
- Dive — github.com/wagoodman/dive (image layer analysis)
Foundation discipline (keep across releases)
- Multi-stage builds: always separate build deps from runtime image. The "node:20 with full npm" image weighs 1GB+; the runtime layer should be ~100MB. Build stage produces artifacts, runtime stage copies them in.
- Non-root user:
RUN addgroup -S app && adduser -S app -G app && USER app— never run app code as root inside the container, even if "it's just a sandbox". - .dockerignore mandatory: forgotten
.git/ornode_modules/in the build context bloats images by hundreds of MB and leaks secrets. The.dockerignorerules mirror your.gitignoreplus build artifacts. - HEALTHCHECK at the Dockerfile level: not just at the orchestrator level. Lets Docker/Compose detect unhealthy containers before the orchestrator does.
- Pin base image major+minor (
node:20-alpine, notnode:latestor barenode:20): floating tags break reproducibility; SHA pinning is overkill for most apps but worth it for security-critical builds. - Secret management: never
COPY .envor hardcode credentials inENV. Use BuildKit secrets (--mount=type=secret) or runtime-injected env vars from the orchestrator.
See also
/ops:ops-deploy— deployment checklist consumes the built image/ops:ops-database— Compose patterns for DB services (depends_on: { condition: service_healthy })qa-security— image scanning gate (Snyk/Trivy) before pushops-ci— Hadolint + image scan as CI steps
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 · 41 lines · 25 tokens per session scan A 4012affd4913
ops-docker is a skill published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 647 once invoked, about $0.0001 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
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
ai-policy-generator
AI governance policy creation for nonprofits and enterprises with frameworks, risk assessment, ethical guidelines, and compliance templates. Use when drafting AI usage policies, responsible AI frameworks, or organizational AI governance documents.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
ios-development
Comprehensive guide for building native Apple platform applications.
battle-card-builder
Competitive battle card creation for sales teams combining competitive intelligence, sales enablement, and document formatting. Use when building battle cards, competitive analysis decks, or win/loss analysis materials.