Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mendixlabs/mxclinpx agentmods add commands/mendixlabs/mxcli/testWrote 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/commands/mendixlabs/mxcli/test)<a href="https://agentmods.dev/commands/mendixlabs/mxcli/test"><img src="https://agentmods.dev/badge/commands/mendixlabs/mxcli/test/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/commands/mendixlabs/mxcli/test"><img src="https://agentmods.dev/badge/commands/mendixlabs/mxcli/test.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.00013 | $0.01072 |
| Opus 5.5 | $0.00005 | $0.00429 |
| Sonnet 5.5 | $0.00003 | $0.00214 |
| Haiku 4.5 | $0.00001 | $0.00107 |
Grade A, and why
test 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 12d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test App
Verify the running Mendix application using playwright-cli.
Prerequisites
- App must be running:
mxcli docker run -p app.mpr --wait - playwright-cli installed (included in devcontainer)
First: does the page work? One call, text, no screenshot
mxcli playwright check /p/Customer_Overview /p/Order_Overview -p app.mpr
mxcli playwright check /p/Customer_Overview -p app.mpr --role User \
--assert-text 'Customers' --assert-count '.mx-name-dgCustomers [role=row]>=1'
One verdict line per page (title, heading, rows, text, console errors, banners);
exit 0 pass, 1 fail, 2 could not check. It signs in itself (--user/--password,
--role, or a demo user from -p) and reuses the saved session. Do not hand-roll
playwright-cli login/goto/sleep/screenshot sequences for this, and screenshot only
for a visual question (--screenshot out.png, read once). The playwright-cli
commands below are for interaction tests.
Session lifecycle
Manage the browser session across commands (attach/reuse, check, tear down):
mxcli playwright open -p app.mpr # open or attach to the session
mxcli playwright status # is it live? what page?
mxcli playwright close [--all] # tear down
Typical loop: open once and log in, then iterate mxcli playwright verify … --keep-open.
Quick Start
# Open browser and take snapshot
playwright-cli open http://localhost:8080
playwright-cli snapshot
# Verify a widget exists (page/DOM assertions run in page context -> eval)
playwright-cli eval "() => document.querySelector('.mx-name-widgetName') !== null"
# Take a screenshot
playwright-cli screenshot
# Close when done
playwright-cli close
Login (Security Enabled)
Only needed for playwright-cli interaction sessions (playwright check signs in
itself). Dispatch an input event after setting .value, or Mendix sees an empty field:
playwright-cli open http://localhost:8080
playwright-cli eval "() => { const el = document.querySelector('#usernameInput'); el.value = 'MxAdmin'; el.dispatchEvent(new Event('input', {bubbles: true})) }"
playwright-cli eval "() => { const el = document.querySelector('#passwordInput'); el.value = 'AdminPassword1!'; el.dispatchEvent(new Event('input', {bubbles: true})) }"
playwright-cli eval "() => document.querySelector('#loginButton').click()"
playwright-cli eval "() => new Promise(r => setTimeout(r, 3000))"
playwright-cli state-save mendix-auth
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.
- 12d ago Changed · +20 lines 3093ebb9f277
- 1mo ago First seen · 97 lines · 13 tokens per session scan A 00e3eea72226
test is a command published in the GitHub repository mendixlabs/mxcli (131 stars, last pushed yesterday), licensed Apache-2.0. It adds 13 tokens to every session and 1,072 once invoked, about $0.0001 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 commands, from other repositories
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…
auto-verify
A command for checking a website's front-end user experience with Playwright, a tool that automates web browsers.
check-ux
Walk the key flows in a real browser at mobile and desktop viewports, then a task per friction point.
create-smoke-test.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
ui-test.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
execute-scenario
Execute BDD test scenarios in a .feature file using browser automation. Use --record to generate a Playwright .spec.js file.