agentmods.dev

e2e-workflow

You are orchestrating the full e2e development workflow for a Mendix pluggable widget in the web-widgets monorepo.

Command for Claude Code

40 yesterday A scan 0 tokens Apache-2.0
View the source file mendix/web-widgets
Install

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.

agentmods
npx agentmods add commands/mendix/web-widgets/e2e-workflow
Clone the repo
git clone --depth 1 https://github.com/mendix/web-widgets

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,382 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01382
Opus 5 $0.00000 $0.00691
Sonnet 5 $0.00000 $0.00276
Haiku 4.5 $0.00000 $0.00138

Measured today against content hash 42a591e7d414, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.claude/commands/mendix/e2e-workflow.md · 143 lines

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/mxcli must exist. If missing, run: bash automation/mxcli/setup.sh
  • The .mpr test 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:

  1. Copy an existing chart/widget MPR as a base (e.g. from column-chart-web/tests/testProject/).
  2. Place it at packages/pluggableWidgets/<widget>/tests/testProject/<WidgetName>.mpr.
  3. Copy the widgets/, deployment/, theme/, and themesource/ folders from the same source.
  4. Replace the source widget's .mpk in widgets/ with the new widget's built .mpk (run pnpm --filter @mendix/<widget> run release first).
  5. Adapt the domain model and microflows via mxcli (see mendix:edit-test-project).
  6. After Studio Pro has opened the MPR and registered the new widget type, push a new branch <widget> to mendix/testProjects so 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>"

Read the full file on GitHub · 143 lines

Changes

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.

  1. today First seen · 143 lines · 0 tokens per session scan A 42a591e7d414

Subscribe to this mod's changes

e2e-workflow is a command published in the GitHub repository mendix/web-widgets (40 stars, last pushed yesterday), 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.

ProductivityTestinglow-codemendixweb-widgets
Related

Other commands, from other repositories

lint

Check the project for naming, security and best-practice issues.

mendixlabs/mxcli · 12 tokens

diff-local

Diff uncommitted mxunit changes against a git reference (MPR v2 only).

mendixlabs/mxcli · 18 tokens

wiki-sync

Re-synthesize pages in docs-wiki/ from their canonical sources.

mendixlabs/mxcli · 13 tokens

explore

Explore and summarise the Mendix project's structure.

mendixlabs/mxcli · 9 tokens

proposal-lint

Audit docs/11-proposals/ for status drift and convention violations.

mendixlabs/mxcli · 13 tokens

check-script

Validate an MDL script before executing it.

mendixlabs/mxcli · 8 tokens