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 bootstrap-appgit 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/bootstrap-app)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/bootstrap-app"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/bootstrap-app/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/bootstrap-app"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/bootstrap-app.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.00058 | $0.06606 |
| Opus 5.5 | $0.00023 | $0.02642 |
| Sonnet 5.5 | $0.00012 | $0.01321 |
| Haiku 4.5 | $0.00006 | $0.00661 |
Grade C, and why
bootstrap-app scanned grade C with 2 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 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 .ai-context # the seed prompt's own `mxcli init --sync-skills` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sI -o /dev/null -w '%{http_code}\n' https://cdn.mendix.com/runtime/mxbuild-$V.tar.gz How it starts
The opening of the file, as written. The whole thing — 456 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 |
|---|---|
| 23-43 | When to Use This Skill |
| 44-130 | Step 0 — interview, and WAIT for the answers |
| 131-263 | Provision |
| 264-333 | If this is a solution (several apps in one repo) |
| 334-391 | Then propose the model — do not build it yet |
| 392-455 | After bootstrap — the inner loop |
Bootstrap a Mendix App in an Empty Repo
When to Use This Skill
Use this when a repo has no Mendix project yet and you have been asked to
provision one with mxcli — typically from the empty-repo seed prompt, which does
nothing but install mxcli, run mxcli init --sync-skills, and send you here.
Everything the seed prompt used to spell out lives here instead, so the prompt stays short enough to paste from a phone and this procedure can be fixed by shipping a new mxcli rather than by re-pasting a longer prompt.
If an .mpr already exists, this is the wrong skill: run mxcli init in the app
folder and go straight to the work.
Related skills: run-local (the warm dev loop this ends in), mdl-entities and
create-page (building the model you propose at the end),
migrate-design-prototype (when a design was handed to you), assess-quality
(reading the report this takes a baseline with), test-microflows and test-app
(the two gates that prove behaviour rather than syntax).
Step 0 — interview, and WAIT for the answers
Ask all of these in ONE message, numbered, each with the default you would pick, so the user can reply "defaults" or answer only what they care about. Do not provision anything until they reply.
The interview comes first for a reason: the app name becomes the .mpr file name, the
Studio Pro app name and the path baked into the SessionStart hook, so it is far
cheaper to ask than to rename afterwards. The rest of the answers are the brief — they
get written into the repo, so the session that resumes after an idle reap knows what
it is building.
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 27c25ab36da9
- 5d ago Changed · +38 lines e6b590572ba4
- 9d ago Changed · +1 lines d46ecb90c198
- 14d ago Changed · +9 lines 0b2b6f37e613
- 15d ago Changed · +1 lines ca1d49193b8c
- 23d ago Changed · +5 lines a57ee9693ee7
- 28d ago Changed · +81 lines · +3 tokens per session 03e83c1c42ab
- 1mo ago Changed · +75 lines 6a83c719e552
- 1mo ago First seen · 246 lines · 55 tokens per session scan C 4d73aec086dc
bootstrap-app is a skill published in the GitHub repository mendixlabs/mxcli (130 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 6,606 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop.
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
workflow-creator
Create or update reusable Dynamic Workflow JavaScript files under .qwen/workflows. Use when the user asks to create, save, edit, or reuse a Dynamic Workflow, including requests started from the Web Shell Workflows page.