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.
git 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/commands/christopherlouet/claude-base/ops-docker)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-docker"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-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/commands/christopherlouet/claude-base/ops-docker"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-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.00000 | $0.00363 |
| Opus 5.5 | $0.00000 | $0.00145 |
| Sonnet 5.5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
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 13d 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 Agent
Dockerization and containerization of projects.
Request context
$ARGUMENTS
Objective
Generate optimized Dockerfiles, docker-compose and .dockerignore tailored to the project's technical stack, with multi-stage builds and security.
Workflow
- Detect the project's technical stack (Node.js, Python, Go, React, etc.)
- Generate an optimized multi-stage Dockerfile (build + production)
- Create a docker-compose.yml with services, volumes and networks
- Configure the .dockerignore
- Apply security best practices (non-root user, no secrets in the image)
- Configure healthchecks
- Optimize the layer order for caching
Expected output
- Dockerfile: optimized production image
- docker-compose.yml: multi-container orchestration
- .dockerignore: configured exclusions
- Information: estimated size, build/run commands
Related agents
| Agent | Usage |
|---|---|
/ops:ops-ci |
CI/CD with Docker |
/ops:ops-env |
Environment management |
/ops:ops-monitoring |
Container monitoring |
IMPORTANT: Always use specific tags for base images (not latest).
YOU MUST scan the image for vulnerabilities before deployment.
NEVER include secrets or credentials in the Docker image.
NEVER use root in production.
See also
Docker Inc.'s own skills — docker/skills (docker-project-foundations, docker-build-strategies, docker-compose-patterns, docker-destructive-guardrails) — hold the Dockerfile and Compose depth; the ops-docker skill points to them and keeps image scanning and Hadolint, which they leave out.
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.
- 13d ago Changed · +4 lines 81eaf51d1572
- 1mo ago First seen · 47 lines · 0 tokens per session scan A f2a2e38a63ac
ops-docker is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 363 tokens. 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 commands, from other repositories
context-stats
Display context window usage and token statistics.
migrate
Generate and manage database migrations.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
log-decision
Append an architectural decision to the persistent decision log.
session-log
Explain where session history lives now that the toolkit keeps no session log.
update-docs
Scan recently modified files and update the matching documentation.