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 choose-edit-modegit 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/choose-edit-mode)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/choose-edit-mode"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/choose-edit-mode/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/choose-edit-mode"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/choose-edit-mode.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.00097 | $0.01599 |
| Opus 5.5 | $0.00039 | $0.00640 |
| Sonnet 5.5 | $0.00019 | $0.00320 |
| Haiku 4.5 | $0.00010 | $0.00160 |
Grade A, and why
choose-edit-mode scanned grade A with 0 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 5d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 113 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 |
|---|---|
| 30-49 | The rule |
| 50-78 | Scripts are mdl 1 — upgrade a headerless file before you edit it |
| 79-94 | Which document types have alter |
| 95-112 | Types with no alter: microflows, nanoflows, menus, Java actions |
Choose the Edit Mode by Who Owns the Document
MDL has two ways to change a document, and each is safe in a different situation.
| Declarative | Patch | |
|---|---|---|
| Statement | create or modify <type> X ( … ) { … }, the whole definition |
alter <type> X …, only the change |
| Source of truth | your .mdl scripts |
the stored model |
| Use for | new apps and modules; documents your scripts created and nobody has edited since | documents made or edited in Studio Pro; marketplace modules |
| Risk | drops whatever the statement does not say, including content MDL cannot express | none for what it does not mention |
The rule
- New app, new module, new document: write declarative MDL. There is nothing to read and nothing to preserve.
- Existing Studio Pro document: change it with
alter. Analterleaves every element it does not name untouched. Measured:alter page … set Captionchanged one string and byte-preserved every other translation on the page. - describe → edit →
create or modifyonly for documents mxcli created and whose stored state is still what your script produced (nobody has changed them in Studio Pro since). On a Studio Pro-authored document this path is lossy even when you change nothing. On real projects it has flipped association storage from table to column, dropped page translations, dropped nanoflow annotation links, changed export levels, and dropped a snippet's type.mxcli diffruns the script on a scratch copy and lists every unit it would write, so run it first and expect "exec would write nothing" for a document you did not mean to change. - Never
dropand re-create an existing document to change it. The new document gets new identities. For an entity, the runtime then drops its table and its rows.
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.
- 5d ago Changed · +13 lines 1bd061f91272
- 14d ago Changed · +2 lines d9b4e5c946ec
- 15d ago Changed · +29 lines · +16 tokens per session 9bae03b5f5b7
- 16d ago First seen · 69 lines · 81 tokens per session scan A 384a3491d772
choose-edit-mode is a skill published in the GitHub repository mendixlabs/mxcli (131 stars, last pushed yesterday), licensed Apache-2.0. It adds 97 tokens to every session and 1,599 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-01.
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.