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 skills add mendixlabs/mxcli --skill test-microflowsgit clone --depth 1 https://github.com/mendixlabs/mxcliWrote 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-microflows)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/test-microflows"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/test-microflows.svg" alt="Measured on agentmods" 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.00053 | $0.04921 |
| Opus 5 | $0.00026 | $0.02461 |
| Sonnet 5 | $0.00011 | $0.00984 |
| Haiku 4.5 | $0.00005 | $0.00492 |
Grade A, and why
test-microflows 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 3d 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 — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Microflows Skill
This skill guides you through writing and running MDL-based microflow tests using mxcli test.
Reference files
reference/annotations.md— every test annotation:@test,@setup,@teardown,@cleanup,@skip, parameters and expected values, with what each one does and the exact spelling. Check an annotation here rather than guessing — an unknown one is a parse error, not a warning.
When to Use This Skill
Use this when:
- The user asks to test microflow logic (not UI/pages)
- The user wants to verify that microflows return correct values
- The user wants to validate entity creation, updates, or control flow
- You have generated MDL microflows and want to verify they work at runtime
- The user asks for unit tests or integration tests on business logic
For UI/page testing (widget rendering, form interactions, browser tests), see the test-app skill instead.
Prerequisites
- Mendix project with microflows to test
- A way to run the app — either of:
--local(no Docker): mxcli boots the runtime itself, the same waymxcli run --localdoes. This is the only option in a container without a Docker daemon, which includes Claude Code web sessions.- Docker: stack initialized (
mxcli docker init -p app.mpr) and the app buildable (mxcli docker build -p app.mpr).
mxcli test tests/ -p app.mpr --local # no daemon needed
mxcli test tests/ -p app.mpr # Docker
--local uses its own ports (app 8081, admin 8091) and its own <project>_test
database, so a mxcli run --local dev loop can keep serving the same project
while the tests run — the tests never write into the database you are looking at
in the browser. The database is created on first use.
The deployment directory is shared, and not by choice: mxbuild always writes
it to <app dir>/deployment and has no option to move it. That used to blank the
running app — a headless test boot does not bundle the web client, and the boot's
packaging pass deletes deployment/web/dist, so the app answered HTTP 200 with
a blank page (Mendix's SPA shell over a 404 for /dist/index.js) while the
tests passed and nothing was reported at either end. The bundle is now copied
aside before the boot and put back after, so the dev loop keeps the exact bundle
it built.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 550 lines · 53 tokens per session scan A a93abf85a7d5
test-microflows is a skill published in the GitHub repository mendixlabs/mxcli (116 stars, last pushed yesterday), licensed Apache-2.0. It adds 53 tokens to every session and 4,921 once invoked, about $0.0003 per session on Opus 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
vue-component-testing
Applies the three-tier test taxonomy for Vue 3 applications: writes unit tests for composables and Pinia stores with Vitest, component tests for behaviour and user interactions with @testing-library/vue, and acceptance tests for full user flows with Playwright. Ensures tests focus on observable behaviour, not…
fix-bug
Investigates and fixes a reported bug. Reads relevant code, identifies the root cause, proposes a fix, and adds or updates tests to prevent regression. Invoked when the user describes unexpected behavior, an error, a crash, or a failing test.
test-generation
Generate and run unit/integration tests TDD-style across Python, Node, and .NET. Use when adding tests to untested code, implementing a feature test-first, or finding coverage gaps.
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.
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.