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 skills/luuow/meridian-mcp/docker-composenpx skills add LuuOW/meridian-mcp --skill docker-composegit clone --depth 1 https://github.com/LuuOW/meridian-mcpWrote 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/luuow/meridian-mcp/docker-compose)<a href="https://agentmods.dev/skills/luuow/meridian-mcp/docker-compose"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/docker-compose.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.00035 | $0.01635 |
| Opus 5 | $0.00017 | $0.00817 |
| Sonnet 5 | $0.00007 | $0.00327 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
docker-compose 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 6d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docker-compose
Production-grade docker-compose.yml authoring for multi-service applications. Covers dependency graphs, conditional service activation, config layering, and zero-downtime update strategies.
Dependency Ordering with Health Checks
depends_on with condition: service_healthy prevents race conditions at startup. Without it, your app starts before the database is ready to accept connections.
services:
api:
build: .
depends_on:
db:
condition: service_healthy
redis:
condition: service_healthy
migrations:
condition: service_completed_successfully # one-shot jobs
db:
image: postgres:16
healthcheck:
test: ["CMD-SHELL", "pg_isready -U $$POSTGRES_USER"]
interval: 5s
timeout: 3s
retries: 5
redis:
image: redis:7-alpine
healthcheck:
test: ["CMD", "redis-cli", "ping"]
interval: 5s
migrations:
image: myapp:latest
command: ["alembic", "upgrade", "head"]
depends_on:
db:
condition: service_healthy
restart: "no" # one-shot — do not restart after completion
Compose Profiles (Selective Service Activation)
Profiles let you activate subsets of services without maintaining separate files.
services:
api:
build: .
# no profile — always started
worker:
build: .
command: celery -A app worker
profiles: [worker] # only started with --profile worker
flower:
image: mher/flower
profiles: [worker, debug] # started with either --profile worker or --profile debug
mailhog:
image: mailhog/mailhog
profiles: [debug] # local email testing only
ports:
- "127.0.0.1:8025:8025"
adminer:
image: adminer
profiles: [debug]
ports:
- "127.0.0.1:8080:8080"
# Start only core services
docker compose up -d
# Start core + worker profile
docker compose --profile worker up -d
# Start everything for local debugging
docker compose --profile worker --profile debug up -d
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.
- 6d ago First seen · 239 lines · 35 tokens per session scan A def5b7cd41e2
docker-compose is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 1,635 once invoked, about $0.0002 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-31.
Other skills, from other repositories
container-manager-swarm
Docker Swarm cluster orchestration via the container-manager-mcp MCP server — initialize/leave a swarm, list nodes and services, and create or remove replicated services across the cluster. Use when the agent must operate a multi-host Swarm from a manager node, inventory cluster services/nodes, or deploy a service. Do…
docker-containerization
Containerize applications with multi-stage Dockerfiles, Docker Compose orchestration, image optimization, and container security. Covers Python, Node.js, and multi-service architectures. Triggers on Docker, containerization, or container orchestration requests.
docker-docs
Comprehensive Docker 28.x reference covering all features: installation, Dockerfile instructions, multi-stage builds, Docker Compose, networking, volumes, CLI commands, image management, registries, security best practices, CI/CD integration, debugging, and Kubernetes migration. Use whenever the user mentions Docker…
compose
Skill "compose" from chaterm/terminal-skills, covering docker compose 编排, 概述, 基础命令, 启动服务 and 停止服务.
docker-compose-services
Run multi-service apps with Docker Compose — services, networks, volumes, healthchecks, and env config.
harbor
CLI toolkit for managing containerized LLM services. Use when the user wants to start, stop, configure, or manage AI/LLM services like Ollama, Open WebUI, llama.cpp, vLLM, LiteLLM, ComfyUI, and 250+ others. Triggers on requests to "run a model", "start ollama", "set up an LLM", "configure harbor", "manage services"…