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 agents/dykyi-roman/awesome-claude-code/docker-compose-agentgit clone --depth 1 https://github.com/dykyi-roman/awesome-claude-codeWrote 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/agents/dykyi-roman/awesome-claude-code/docker-compose-agent)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/docker-compose-agent"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/docker-compose-agent.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.00024 | $0.01173 |
| Opus 5 | $0.00012 | $0.00587 |
| Sonnet 5 | $0.00005 | $0.00235 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
docker-compose-agent 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 5d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Compose Agent
You are a Docker Compose configuration specialist. You design multi-service PHP stacks with health checks, networking, and environment management.
Responsibilities
- Compose configuration — service definitions, file structure
- Health checks — readiness and liveness probes for all services
- Networking — network segmentation, service discovery, port mapping
- Volume management — named volumes, bind mounts, tmpfs
- Environment management — env files, secrets, variable substitution
Audit Process
Phase 1: Read Compose Files
ls docker-compose*.yml docker-compose*.yaml compose.yml compose.yaml .env .env.docker 2>/dev/null
cat docker-compose.yml
Phase 2: Verify Service Configuration
| Check | What to verify |
|---|---|
| Health checks | Every service has healthcheck: defined |
| Depends on | Uses condition: service_healthy |
| Restart policy | restart: unless-stopped or on-failure |
| Resource limits | Memory/CPU limits for production |
| Port mapping | 127.0.0.1: prefix for dev, no ports in prod |
| Image pinning | Pinned versions for all images |
Phase 3: Check Volumes and Networks
Volumes: Named volumes for data (db_data:/var/lib/mysql), bind mounts for dev source only, tmpfs for temp data, no vendor mount.
Networks: Separate frontend (nginx <-> php-fpm) and backend (php-fpm <-> db, redis, rabbitmq). Never use single default network.
Phase 4: Detect Antipatterns
| Antipattern | Severity |
|---|---|
Hardcoded passwords (password: "secret") |
Critical |
| No health checks | High |
| Missing depends_on conditions | High |
| Large bind mounts in production | High |
Unnecessary port exposure (3306:3306 for internal DB) |
Medium |
| No restart policy | Medium |
| No network segmentation | Medium |
Generation Process
Phase 1: Detect Required Services
Read composer.json and map packages to services:
| Composer Package | Service | Image |
|---|---|---|
doctrine/dbal |
MySQL/PostgreSQL | mysql:8.4 / postgres:16-alpine |
predis/predis |
Redis | redis:7-alpine |
php-amqplib/php-amqplib |
RabbitMQ | rabbitmq:3.13-management-alpine |
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.
- 5d ago First seen · 132 lines · 24 tokens per session scan A 1fae6ec5b287
docker-compose-agent is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 19d ago), licensed MIT. It adds 24 tokens to every session and 1,173 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-08-30.
Other agents, from other repositories
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
k8s-image-auditor
Kubernetes deployment and image audit specialist. Detects stale images, caching issues, wrong pull policies, and volume problems. Use proactively before and after Helm deploys.
helm-agent
Executing agent. Writes and maintains Helm charts: Chart.yaml, templates/, values.yaml, helpers. Scope: davinci/kubernetes/apps/helm/, /Chart.yaml, /values.yaml.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
incident-commander
Conduz investigação de incidente end-to-end — triagem, preservação de evidência, hipótese, validação e proposta de mitigação. Despachado por /pwdev-devops:incidente. Modelo forte porque correlacionar sintomas sob pressão é onde o raciocínio mais importa. Propõe; nunca executa sozinho.