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/mendixlabs/mxcli/docker-workflownpx skills add mendixlabs/mxcli --skill docker-workflowgit clone --depth 1 https://github.com/mendixlabs/mxcliWhat 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 | $0.00048 | $0.04586 |
| Opus 5 | $0.00024 | $0.02293 |
| Sonnet 5 | $0.00010 | $0.00917 |
| Haiku 4.5 | $0.00005 | $0.00459 |
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 yesterday.
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 — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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)
The Mendix container uses a volume mount (not COPY) — .docker/build/ is mounted directly into the container at /mendix. This means after rebuilding the PAD, you only need to restart the container (no Docker image rebuild). The generated Dockerfile is kept in the build output for production image builds.
Quick Start: One Command
The easiest way to get a Mendix app running in Docker:
# Setup, build, and start in one command
mxcli docker run -p app.mpr
# with startup confirmation (waits for "runtime successfully started")
mxcli docker run -p app.mpr --wait
# Fresh start (removes database volumes first)
mxcli docker run -p app.mpr --fresh --wait
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.
- yesterday First seen · 436 lines · 48 tokens per session scan C e135402e1281
docker-workflow is a skill published in the GitHub repository mendixlabs/mxcli (115 stars, last pushed 2d ago), licensed Apache-2.0. It adds 48 tokens to every session and 4,586 once invoked, about $0.0002 per session on Opus 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
zh-output-example
Reviews Chinese skill documentation for publication readiness. Invoke when the user asks in Chinese to review a skill.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
powerpoint
Create designed, editable PowerPoint .pptx presentations with PptxGenJS. Use when the user asks to create, generate, update, or inspect a deck, slide deck, presentation, or .pptx file.
review-offered-task
Review a task that has been offered to you and decide whether to accept or reject it.
Swift Performance Optimization Skill
Use when investigating measured Swift or Apple-platform regressions in CPU, memory, launch, scrolling, animation hitches, image processing, energy, networking, or concurrency, or when designing performance tests and Instruments experiments. Do not use for speculative micro-optimization, ordinary refactoring, or a…
systematic-debugging
Root-cause a bug already in front of you, instead of guessing at fixes. Use on triggers like "root cause this", "why is this failing", "debug systematically", "this test is flaky", "it works locally but not in CI", or when a fix attempt has already failed once. Enforces a phased evidence-first process before any code…