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 agentmods add commands/mendix/web-widgets/e2e-specgit clone --depth 1 https://github.com/mendix/web-widgetsWhat 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 | $0.00000 | $0.00714 |
| Opus 5 | $0.00000 | $0.00357 |
| Sonnet 5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
e2e-spec 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 today.
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are helping the developer write or improve Playwright e2e specs for a Mendix pluggable widget in the web-widgets monorepo.
Read first: docs/requirements/e2e-test-guidelines.md — owns all rules for imports, assertions, locators, navigation, and snapshots. Do not duplicate them here.
Context
- Specs live at:
packages/pluggableWidgets/<widget>/e2e/*.spec.js - Playwright strict mode is ON
<widget>throughout this document is the package folder name, e.g.badge-web,datagrid-web.
Discovering selectors and navigation from the test project
Before writing selectors, look up the actual widget names and menu labels in the .mpr:
# Full overview: modules, pages, entities, navigation menu labels
bash automation/mxcli/mx-testproject.sh inspect badge-web # replace with actual widget name
# Widget structure of a specific page (reveals .mx-name-* values)
bash automation/mxcli/mx-testproject.sh exec <widget> "DESCRIBE PAGE <Module>.<PageName>"
# List pages if you don't know the page name
bash automation/mxcli/mx-testproject.sh list-pages <widget>
# Search for a widget name across all project strings
bash automation/mxcli/mx-testproject.sh search <widget> 'keyword'
The inspect output includes DESCRIBE NAVIGATION Responsive at the end — use those exact strings in page.getByRole("menuitem", { name: "..." }).
Spec file split
Standard naming convention per widget:
<widget>.spec.js— core rendering and data bindingonClick.spec.js— microflow, nanoflow, keyboard accessibilitydataTypes.spec.js— each supported Mendix attribute typelayouts.spec.js— widget inside list view, tab, data view, listen-to-grid
Running tests
# Full CI run (Docker):
pnpm --filter @mendix/badge-web run e2e # replace with actual widget name
# Skip re-downloading the test project (useful when iterating locally):
pnpm --filter @mendix/<widget> run e2e --no-setup-project
# Skip re-downloading and rebuilding (fastest iteration; requires local test project files):
pnpm --filter @mendix/<widget> run e2e --no-setup-project --no-update-project
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.
- today First seen · 66 lines · 0 tokens per session scan A 48c819b88e56
e2e-spec 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 714 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-handoff
Generate copy-paste-ready Studio Pro instruction sheets when a human-in-loop step is required. Exact paths, classes, widgets, bindings -- no vague guidance. Auto-runs verification (mx-doctor + impact + playwright) after the human replies "done".
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.
e2e
使用 Playwright 对 Web UI 进行端到端测试（支持视频录制、Trace 录制、控制台/网络日志捕获）.
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
research-perplexity
Run a deep research query using Perplexity's /research mode via Playwright browser automation. This is an alternative to /export-to-council that uses Perplexity's dedicated research mode instead of multi-model council.