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 skills add mendixlabs/mxcli --skill docker-workflowgit clone --depth 1 https://github.com/mendixlabs/mxcliWrote 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/mendixlabs/mxcli/docker-workflow)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/docker-workflow"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/docker-workflow/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.
<a href="https://agentmods.dev/skills/mendixlabs/mxcli/docker-workflow"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/docker-workflow.svg" alt="Reviewed on agentmods" width="80" 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.00048 | $0.05000 |
| Opus 5.5 | $0.00019 | $0.02000 |
| Sonnet 5.5 | $0.00010 | $0.01000 |
| Haiku 4.5 | $0.00005 | $0.00500 |
Grade C, and why
docker-workflow scanned grade C with 1 finding 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /path/to/project/.docker/build/lib/runtime How it starts
The opening of the file, as written. The whole thing — 458 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find it fast
sed -n '<from>,<to>p' SKILL.md one section rather than reading the file;
./mxcli syntax <topic> answers how do I write this for a fraction of either.
| lines | section |
|---|---|
| 29-36 | When to Use This Skill |
| 37-52 | Prerequisites |
| 53-68 | Architecture |
| 69-85 | Quick Start: One Command |
| 86-113 | Creating an Empty Mendix App |
| 114-274 | Step-by-Step Workflow |
| 275-305 | Common Workflow: Edit, Rebuild, Test |
| 306-417 | Hot Reload |
| 418-436 | Environment Variables |
| 437-457 | Troubleshooting |
Docker Build & Run Skill
This skill guides you through building, running, and testing a Mendix application using Docker inside a devcontainer.
When to Use This Skill
Use this when:
- The user wants to run their Mendix app locally in Docker
- The user wants to build a deployable container image
- The user asks about testing or validating their app
- The user needs to set up the Docker workflow for the first time
Prerequisites
The devcontainer created by mxcli init includes:
- JDK 21 (Adoptium temurin-21-jdk) — required by MxBuild
- Docker-in-Docker (or Podman-in-Podman) — container runtime inside the devcontainer
- Port forwarding — ports 8080 (app) and 8090 (admin) auto-forwarded
Podman Support
mxcli auto-detects Docker or Podman. To force Podman:
export MXCLI_CONTAINER_CLI=podman
When using mxcli init, pass --container-runtime podman to generate a devcontainer with Podman-in-Podman instead of Docker-in-Docker. Requires Podman 4.7+ (ships podman compose natively).
Architecture
host machine (browser at localhost:8080)
└── Docker or Podman (host daemon)
└── Devcontainer (VS Code)
├── mxcli, JDK 21, project files
└── Docker/Podman daemon (docker-in-docker or podman-in-podman)
└── docker/podman compose stack
├── mendix container (8080, 8090)
│ └── /mendix ← volume mount from .docker/build/
└── postgres container (5432)
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.
- 3d ago Changed · +3 lines 63197413762c
- 5d ago Changed · +19 lines a44d8c19bccc
- 1mo ago First seen · 436 lines · 48 tokens per session scan C e135402e1281
docker-workflow is a skill published in the GitHub repository mendixlabs/mxcli (130 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 5,000 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
hatch3r-cli-toolbox
Category-indexed reference for 34 specialist CLI tools beyond the always-on five (ripgrep, jq, gh, fd, fzf). Use to pick the right tool for HTTP clients, ai-chat, structural-search, sed-style edits, data ops, browser automation, container ops, and more.
hatch3r-containerize
Containerizes an application through a repeatable workflow — multi-stage Dockerfile, non-root hardening, minimal base image, .dockerignore, healthcheck, local docker-compose, Kubernetes manifest basics, and an image-scan gate. Use when adding or hardening container artifacts.
write-dockerfile
Creates or updates an optimized, production-ready Dockerfile and .dockerignore. Focuses on image build strategy, runtime hardening, caching, and minimal production images. Invoked when the user asks to write a Dockerfile, improve container image quality, or harden image builds.
docker-compose-local-setup
Creates or updates local multi-service orchestration using docker compose. Covers compose.yaml design, service health checks, dependson readiness, env files, named volumes, migrations/seeds jobs, verification commands, and cleanup workflows for local development.
mux-docker
Launch and manage Mux Swarm CLI instances in Docker containers with full bidirectional communication. Enables spawning isolated agent sessions, switching between agents, and orchestrating multi-agent workflows in containerized environments. Use when you need process isolation, reproducible environments, or want to run…
docker-sandbox
Run code in isolated Docker containers with pre-installed dependencies. Use for all tasks requiring any code execution, specific libraries, or file generation.