Borrowing it
Nothing to install: this file belongs to mendix/web-widgets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mendix/web-widgets/main/.claude/commands/mendix/e2e-workflow.mdgit clone --depth 1 https://github.com/mendix/web-widgetsWrote 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/mendix/web-widgets/e2e-workflow)<a href="https://agentmods.dev/commands/mendix/web-widgets/e2e-workflow"><img src="https://agentmods.dev/badge/commands/mendix/web-widgets/e2e-workflow/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/mendix/web-widgets/e2e-workflow"><img src="https://agentmods.dev/badge/commands/mendix/web-widgets/e2e-workflow.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.00000 | $0.01382 |
| Opus 5.5 | $0.00000 | $0.00553 |
| Sonnet 5.5 | $0.00000 | $0.00276 |
| Haiku 4.5 | $0.00000 | $0.00138 |
Grade A, and why
e2e-workflow 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 1mo 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are orchestrating the full e2e development workflow for a Mendix pluggable widget in the web-widgets monorepo.
Widget name passed by user: $ARGUMENTS
If no widget name is provided, ask the user which widget they are working on (e.g., badge-web, datagrid-web).
Prerequisites
automation/tools/mxclimust exist. If missing, run:bash automation/mxcli/setup.sh- The
.mprtest project must be closed in Studio Pro before any mxcli edits. Check with:ls packages/pluggableWidgets/<widget>/tests/testProject/.mendix-cache/lock 2>/dev/null \ && echo "⚠️ Studio Pro lock file present — close the project first" \ || echo "OK — no lock file" - Docker must be running for the full CI e2e run
Phase 1 — Download and inspect the test project
Download the test project (if not already present):
pnpm --filter @mendix/<widget> run e2edev --setup-project
If this fails with 404 Not Found / Cannot find test project in GitHub repository, the branch does not exist yet in mendix/testProjects. In that case:
- Copy an existing chart/widget MPR as a base (e.g. from
column-chart-web/tests/testProject/). - Place it at
packages/pluggableWidgets/<widget>/tests/testProject/<WidgetName>.mpr. - Copy the
widgets/,deployment/,theme/, andthemesource/folders from the same source. - Replace the source widget's
.mpkinwidgets/with the new widget's built.mpk(runpnpm --filter @mendix/<widget> run releasefirst). - Adapt the domain model and microflows via mxcli (see
mendix:edit-test-project). - After Studio Pro has opened the MPR and registered the new widget type, push a new branch
<widget>tomendix/testProjectsso CI can download it.
Then inspect:
bash automation/mxcli/mx-testproject.sh inspect <widget>
This shows modules, pages, entities, and navigation menu labels in one call. For a specific page's widget structure:
bash automation/mxcli/mx-testproject.sh exec <widget> "DESCRIBE PAGE <Module>.<PageName>"
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.
- 1mo ago First seen · 143 lines · 0 tokens per session scan A 42a591e7d414
e2e-workflow is a command published in the GitHub repository mendix/web-widgets (40 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,382 tokens. 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-01.
Other commands, from other repositories
test
Run the app's microflow tests and verify it in the browser.
mx-test-page
Drive Playwright against the testbed (port 8082). MANDATORY testbed-fingerprint guard (URL :8082 + "Test Project" ribbon) before any other assertion -- safety gate against driving the live project.
playwright-test-heal
Run all my tests and fix the failing ones.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
verify-pr
Verify a PR's frontend changes through browser automation.
test-run
Run E2E tests with qa-use CLI.