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/bootstrap-appnpx skills add mendixlabs/mxcli --skill bootstrap-appgit 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.00055 | $0.03469 |
| Opus 5 | $0.00028 | $0.01734 |
| Sonnet 5 | $0.00011 | $0.00694 |
| Haiku 4.5 | $0.00006 | $0.00347 |
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 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 .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-11.13.0.tar.gz How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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).
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.
- One app, or a solution of several? One Mendix app is the default. "Solution" means several apps in one repo — e.g. a backend that owns the data and publishes OData/REST, and a frontend that consumes it. If so, ask for each app's name and one line on what it owns, and follow "If this is a solution" below.
- App name. Becomes the
.mprfile name, the app name in Studio Pro, and the path in the session hook, so it is awkward to change later. One PascalCase word, letters and digits only —OrderPortal,FieldService,ClubAdmin. Propose one derived from the answer to Q3. - What is the app for? One or two sentences: who uses it, and what it lets them do. If the answer is vague ("a tool for work"), ask one follow-up — everything below is derived from this.
- What does it keep track of? Three to six nouns that will become entities, and a word on how they relate (e.g. "a Job has many Visits; each Visit has Photos"). For a solution, also ask which app owns each noun.
- Who logs in? The user roles, and roughly what each may do (e.g. "Requester creates and sees their own; Approver sees everything and approves").
- Look and feel. One of the bundled themes:
signal(light, high contrast),ledger(light, dense, data-heavy),console(dark), ornonefor stock Atlas. Defaultsignal. - Mendix version. Default
11.13.0.
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 · 246 lines · 55 tokens per session scan C 4d73aec086dc
bootstrap-app is a skill published in the GitHub repository mendixlabs/mxcli (115 stars, last pushed 2d ago), licensed Apache-2.0. It adds 55 tokens to every session and 3,469 once invoked, about $0.0003 per session on Opus 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
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…