agentmods.dev

compose-check

compose-check is a skill for Claude Code, Codex from chipi/agentic-ai-homelab. It costs 75 tokens per session (769 once invoked), scanned A, original, MIT.

A read-only pre-deployment check for Docker Compose files. Docker Compose defines and runs groups of related containers as one application.

In plain words
What is it for?
Use it before deploying or editing a Compose stack. It validates each compose file and distinguishes a missing local .env file from an actual configuration error.
Why use it?
It catches invalid YAML, broken variable substitution, and missing environment files before the stack is started.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 2repo 2d ago A scan 75 tokens original MIT

Good fit Use it before deploying or editing a Compose stack. It validates each compose file and distinguishes a missing local .env file from an actual configuration error.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chipi/agentic-ai-homelab/compose-check
View source ↗ chipi/agentic-ai-homelab
Install

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.

Any agent
npx skills add chipi/agentic-ai-homelab --skill compose-check
Clone the repo
git clone --depth 1 https://github.com/chipi/agentic-ai-homelab

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for compose-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/compose-check/github.svg)](https://agentmods.dev/skills/chipi/agentic-ai-homelab/compose-check)
Your own site
<a href="https://agentmods.dev/skills/chipi/agentic-ai-homelab/compose-check"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/compose-check/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.

agentmods 80×15 button for compose-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/chipi/agentic-ai-homelab/compose-check"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/compose-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 769 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.00769
Opus 5 $0.00037 $0.00385
Sonnet 5 $0.00015 $0.00154
Haiku 4.5 $0.00007 $0.00077

Measured 8d ago against content hash ee67012ce719, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

compose-check 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 8d 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.

workstation/claude/skills/compose-check/SKILL.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

compose-check

Catch a broken compose stack before docker compose up, not after. Validates syntax, interpolation, and env wiring — strictly read-only. This skill never runs up, down, pull, or anything that mutates a stack or shared state.

When this applies

Editing a docker-compose*.yml / compose.ya?ml, or about to deploy one, or asked to "check / validate the compose stack." Cheap; run it whenever in doubt.

Check each stack

  1. Find stacks — docker-compose.yml, docker-compose.*.yml, compose.yml, compose.yaml (skip dated backups like *.yml.<date>). If none, say so.
  2. Validate structure, then classify — for each file: 
    docker compose -f <file> config -q
    A fresh checkout usually has no .env (gitignored, present only on the deploy host), so separate "not ready" from "broken":
    • exit 0 → structure + interpolation valid → PASS
    • fails only with env file ... not found → the YAML is fine, the stack just needs an .env absent from this checkout → ENV-MISSING (warn, name the exact path). Not a defect.
    • any other error (YAML parse, additional property, bad interpolation, required variable is missing) → FAIL — surface the message.
  3. Undefined interpolation — grep for ${VAR} used without a default or required marker (${VAR:-default} / ${VAR:?msg}). Any bare ${VAR} not set in the environment or an .env becomes an empty string at runtime. List them.
  4. Env readiness — collect every .env path the stacks declare (top-level --env-file, service env_file:) and report which exist vs are missing. When a stack is ENV-MISSING and a sibling .env.example exists, the fix is cp .env.example .env (then fill secrets) — say that explicitly.

Report

  • Show full command output; end with one line per stack: COMPOSE CHECK <stack>: PASS | ENV-MISSING | FAIL.
  • On FAIL, name the defect (the YAML error or the undefined ${VAR}), not just the exit code. On ENV-MISSING, name the .env to create and the .env.example to copy from.

Read the full file on GitHub · 58 lines

Changes

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.

  1. 8d ago First seen · 58 lines · 75 tokens per session scan A ee67012ce719

Subscribe to this mod's changes

compose-check is a skill published in the GitHub repository chipi/agentic-ai-homelab (2 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 769 once invoked, about $0.0004 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.

Claude CodeContainersDevOps and cloudagentic-aigrafana-alloyhomelablibrechatmcp
Related

Other skills, from other repositories

github-actions-templates

Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.

wshobson/agents · 44 tokens

aiq-deploy

Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.

NVIDIA/skills · 27 tokens

dynamo-recipe-runner

Select, validate, patch, and deploy existing NVIDIA Dynamo Kubernetes recipes. Use for model/backend/GPU/deployment-mode recipe bring-up; use router-starter for router-only mode work and troubleshoot for broken deployments.

NVIDIA/skills · 49 tokens

holoscan-install-container

Install Holoscan SDK via the NGC Docker container. Use for container-based installs; not for native apt/pip/Conda installs.

NVIDIA/skills · 35 tokens

doca-argus

Use this skill when the user is deploying or operating the DOCA Argus Service — the packaged BlueField-side runtime-security container that watches the BlueField and attached host for suspicious activity, integrity violations, and operational anomalies, and forwards findings to a SIEM (Splunk / ELK / Sentinel /…

NVIDIA/skills · 213 tokens

doca-urom-svc

Operate the DOCA UROM Service container on BlueField Arm for remote memory operations (puts, gets, atomics, collectives) enqueued by a paired host using doca-urom: pull the NGC image, choose the UCX component, size queues, configure Comch pairing, and align host and service versions. SECURITY: the service has no…

NVIDIA/skills · 153 tokens