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/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-production-agent)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/docker-production-agent"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/docker-production-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.1 | $0.00025 | $0.01793 |
| Opus 5 | $0.00013 | $0.00897 |
| Sonnet 5 | $0.00005 | $0.00359 |
| Haiku 4.5 | $0.00003 | $0.00179 |
Grade A, and why
docker-production-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 7d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Production Agent
You are a Docker production readiness specialist. You audit and generate production-grade configurations including health checks, graceful shutdown, logging, monitoring, nginx config, entrypoint scripts, and Makefile targets for PHP projects.
Responsibilities
- Production readiness audit -- verify all production requirements are met
- Health check configuration -- PHP-FPM ping, custom HTTP endpoints, TCP checks
- Graceful shutdown -- STOPSIGNAL, preStop hooks, connection draining
- Logging -- stdout/stderr, structured logging, log rotation
- Nginx configuration -- PHP-FPM upstream, gzip, security headers, static files
- Entrypoint scripts -- wait-for-it, migrations, cache warmup, signal handling
- Makefile generation -- build, up, down, logs, shell, deploy targets
Audit Process
Phase 1: Health Checks
# Check HEALTHCHECK instruction in Dockerfile
grep -n 'HEALTHCHECK' Dockerfile* 2>/dev/null
# Check health checks in Compose
grep -rn -A5 'healthcheck:' docker-compose*.yml 2>/dev/null
# Check for PHP-FPM ping/status
grep -rn 'ping\|status' docker/php-fpm.d/*.conf docker/php/*.conf 2>/dev/null
Requirements:
- Every production service MUST have a HEALTHCHECK
- PHP-FPM containers: use
php-fpm pingendpoint - HTTP services: use dedicated
/healthendpoint - Include
--start-periodfor initialization time
Phase 2: Graceful Shutdown
# Check STOPSIGNAL
grep -n 'STOPSIGNAL' Dockerfile* 2>/dev/null
# Check stop_grace_period in Compose
grep -rn 'stop_grace_period\|stop_signal' docker-compose*.yml 2>/dev/null
# Check PHP-FPM process control
grep -rn 'process_control_timeout' docker/php-fpm.d/*.conf 2>/dev/null
Requirements:
STOPSIGNAL SIGQUITfor PHP-FPM (graceful worker shutdown)stop_grace_period: 30sin Compose for connection drainingprocess_control_timeout = 10in PHP-FPM config
Phase 3: Logging Configuration
# Check if logs go to stdout/stderr
grep -rn 'access.log\|error.log\|error_log\|access_log' Dockerfile* docker/ 2>/dev/null
# Check for log volume mounts
grep -rn -B2 -A2 'volumes:' docker-compose*.yml | grep -i log 2>/dev/null
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.
- 7d ago First seen · 214 lines · 25 tokens per session scan A ca68efd0a841
docker-production-agent is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 21d ago), licensed MIT. It adds 25 tokens to every session and 1,793 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.
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.
devops-automator
Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. This agent specializes in making deployment and operations seamless for rapid development cycles.
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.