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 custom-widgetsgit 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/custom-widgets)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/custom-widgets"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/custom-widgets/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/custom-widgets"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/custom-widgets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00142 | $0.08123 |
| Opus 5.5 | $0.00057 | $0.03249 |
| Sonnet 5.5 | $0.00028 | $0.01625 |
| Haiku 4.5 | $0.00014 | $0.00812 |
Grade A, and why
custom-widgets 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 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.
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 — 721 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 |
|---|---|
| 27-151 | Any installed widget is named by its own name |
| 152-253 | Built-in Pluggable Widgets |
| 254-342 | Charts (Mendix Charts.mpk) |
| 343-490 | Adding a Third-Party Widget |
| 491-516 | Authoring over MCP (live Studio Pro) |
| 517-619 | .def.json Reference |
| 620-680 | Engine Internals |
| 681-696 | Verify & Debug |
| 697-708 | Common Mistakes |
| 709-720 | Key Source Files |
Custom & Pluggable Widgets in MDL
Any installed widget is named by its own name
If a widget is installed in widgets/, MDL names it directly — no keyword list,
no widget id:
htmlelement frame (tagName: 'div', tagContentMode: 'container') {
attribute a1 (attributeName: 'data-testid', attributeValueType: 'expression')
tagcontentcontainer body {
dynamictext caption (Content: 'Inside the element')
}
}
Three things there are read from the widget's definition, not from anything
hardcoded: the keyword (htmlelement, the last segment of the widget id),
the properties (the widget's own spelling — tagName, not TagName), and
the body containers — attribute is an object list (one entry per
repetition), tagcontentcontainer a child slot (holds widgets).
Ask the widget rather than guessing. describe widget type <name> lists every
property with its type, default and enumeration members; every body container
and whether MDL can express it; and a complete example that parses AND checks as
written:
mxcli widget describe htmlelement -p app.mpr
Do this first when placing an unfamiliar widget. It is faster than reading this
file and it cannot go stale, because it reads the .mpk the project actually
has.
The id form is the fallback
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 Changed · +3 lines 2f060622a0f1
- 5d ago Changed · +19 lines 26751f45e93d
- 13d ago Changed 9106cdf5c2cf
- 15d ago Changed · +5 lines a9c4d04b5242
- 23d ago Changed · +11 lines 46ac73a17fc1
- 28d ago Changed · +61 lines 275505213e76
- 1mo ago Changed · +23 lines add5c492f737
- 1mo ago Changed · +18 lines cdd0d37a69bb
- 1mo ago Changed · +86 lines · +41 tokens per session 60244bb09050
- 1mo ago First seen · 495 lines · 101 tokens per session scan A a33ca2605036
custom-widgets is a skill published in the GitHub repository mendixlabs/mxcli (130 stars, last pushed yesterday), licensed Apache-2.0. It adds 142 tokens to every session and 8,123 once invoked, about $0.0006 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-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.