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 skills/mendixlabs/mxcli/test-appWrote 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/test-app)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/test-app"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/test-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/test-app"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/test-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 34 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
- medium MCP Rug Pull · line 435 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
- medium MCP Rug Pull · line 53 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 330 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
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.00086 | $0.05567 |
| Opus 5.5 | $0.00034 | $0.02227 |
| Sonnet 5.5 | $0.00017 | $0.01113 |
| Haiku 4.5 | $0.00009 | $0.00557 |
Grade A, and why
test-app 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 8d 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 — 537 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 |
|---|---|
| 32-42 | When to Use This Skill |
| 43-84 | Start Here: mxcli playwright check (one call, text, no screenshot) |
| 85-135 | Prerequisites |
| 136-160 | Quick Start |
| 161-182 | Widget Name Selectors |
| 183-298 | Verification Patterns |
| 299-372 | CI/CD: Test Scripts |
| 373-416 | Session Management |
| 417-444 | Debugging |
| 445-477 | Selector Rules |
| 478-494 | Known Gotchas |
| 495-528 | Feedback Loop Workflow |
| 529-536 | Related Skills |
Test App Skill
This skill guides you through verifying a running Mendix application using playwright-cli for browser automation and mxcli oql for data assertions.
When to Use This Skill
Use this when:
- The user asks to test, verify, or validate a running Mendix app in the browser
- The user wants to confirm that generated pages and widgets actually render
- The user asks for end-to-end or integration tests involving the UI
- The user wants to verify that data is persisted correctly after UI interactions
- You have generated MDL that creates pages and want to close the feedback loop
For microflow logic testing (business rules, calculations, entity operations — no browser needed), use the test-microflows skill and mxcli test instead.
Start Here: mxcli playwright check (one call, text, no screenshot)
"Does the page render?", "is there an error?", "did the list get rows?" are answered by one command against the running app — not by a playwright-cli session:
mxcli playwright check /p/customers /p/orders -p app.mpr
page /p/customers title="Customers" h="Customer overview" rows=12 text=812 console-errors=0
page /p/orders title="Orders" text=254 console-errors=1
ALERT An error occurred, please contact your system administrator.
ERR [Client] An error occurred while executing microflow data source for widget …
HTTP 560 POST /xas/
FAIL 1 error banner(s)
FAIL 1 console error(s)
FAIL 1 failed request(s)
FAIL 1 of 2 page(s)
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.
- 8d ago Changed · +22 lines 75eb51804aea
- 13d ago Changed · +48 lines · +41 tokens per session d43ef74cc824
- 19d ago Changed 3e3f6c79c3fe
- 1mo ago First seen · 467 lines · 45 tokens per session scan A 265c440af00b
test-app is a skill published in the GitHub repository mendixlabs/mxcli (131 stars, last pushed 2d ago), licensed Apache-2.0. It adds 86 tokens to every session and 5,567 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
hatch3r-browser-verify
Opt-in browser verification skill — spec-run-first Playwright verification (assertions execute in the runner, agent reads only failures), axe-core a11y audits, toHaveScreenshot() regression diffs, E2E test scaffolds, and snapshot-mode exploratory driving. Default ON for UI-affecting agent invocations; disable globally…
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…
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.
tmux-real-user-testing
A real-user test workflow for Qwen Code's terminal interface, using tmux to drive the program and capture readable screen snapshots. tmux is a tool for running and observing terminal sessions.
agent-reproduce-align
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.