More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Docker Compose Safety Check

    1

    Catch risky docker-compose settings before you deploy: passwords in environment, privileged containers, a mounted Docker socket, databases published to the internet, host network mode and :latest images.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Docker Compose Safety Check

    Docker Compose Safety Check

    Example session with this skill installed

    Check this project with docker-compose-safety-check.

    • Read your context and instructions
    • Compiled the docker compose safety

    $ python3 scripts/check_compose.py examples/risky
    BLOCK docker-compose.yml:6 C01 SECRET_IN_COMPOSE
    POSTGRES_PASSWORD=<redacted, 19 chars>
    Why: A password, token or key is written into the Compose file. Anyone who can read the repository can read it, and it stays in git history after you remove it.
    Safer: Rotate the secret, then reference it as ${NAME} with the value in an .env file that git ignores, or use Compose secrets (a *_FILE variable pointing at /run/secrets/...).

    BLOCK docker-compose.yml:19 C02 PRIVILEGED_CONTAINER
    BLOCK docker-compose.yml:25 C03 DOCKER_SOCKET_MOUNTED
    REVIEW docker-compose.yml:4 C11 UNPINNED_IMAGE
    REVIEW docker-compose.yml:7 C17 DATABASE_AUTH_DISABLED
    REVIEW docker-compose.yml:9 C12 DATABASE_PORT_PUBLISHED
    REVIEW docker-compose.yml:11 C11 UNPINNED_IMAGE
    REVIEW docker-compose.yml:12 C13 HOST_NAMESPACE
    REVIEW docker-compose.yml:16 C18 DEFAULT_PASSWORD
    REVIEW docker-compose.yml:21 C14 DANGEROUS_CAPABILITY
    REVIEW docker-compose.yml:23 C15 SECURITY_PROFILE_DISABLED
    REVIEW docker-compose.yml:26 C16 HOST_SYSTEM_MOUNT

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 1 file, 1 with Compose content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    BLOCK docker-compose.yml

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A Postgres port published as "5432:5432" is open on every network interface, and Docker's port rules skip most host firewalls. This skill finds that and ten other risky Compose settings, and tells you how to fix each one.

    Your agent runs a scanner on your docker-compose.yml and compose.yaml files (overrides included). It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach for every finding. Secret values are never printed: the report shows the variable name and length only.

    What it checks

    BLOCK

    • C01: a password, token or key written as a literal value in environment, or inside a database URL
    • C02: privileged: true
    • C03: the Docker socket mounted into a container

    REVIEW

    • C11: an image with no tag or :latest
    • C12: a database or cache port published on every interface
    • C13: network_mode, pid or ipc set to host
    • C14: dangerous capabilities such as SYS_ADMIN or ALL
    • C15: seccomp, AppArmor or SELinux turned off
    • C16: host system folders such as / or /etc mounted
    • C17: a database that accepts logins with no password
    • C18: a well-known default password such as postgres or changeme

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason and safer approach for each rule
    • A risky and a safe example Compose file, and the real report the scanner produces on the risky one

    Limits It reads each Compose file on its own. It does not merge override files or resolve extends, include or ${VAR} values (YAML anchors and merge keys are followed), and it cannot see host firewall rules. NOT FLAGGED is not a guarantee.

    Static check of Compose YAML text. Override files are not merged, and extends, include and ${VAR} values are not resolved. NOT FLAGGED is not a guarantee.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Requires

    python3 (3.9 or newer)

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example Compose file includes a clearly fake, inert password (not-a-real-password) for the scanner to find.

    Listed8 days ago
    Updated4 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads the Compose YAML text. It does not run docker, start containers or pull images.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    The scanner, a rules guide with the reason and safer approach for every rule, a risky and a safe example, and the real report the scanner prints on the risky example.

    New in DevOps & Cloud