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 validation-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/validation-microflows)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/validation-microflows"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/validation-microflows.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.02055 |
| Opus 5 | $0.00019 | $0.01027 |
| Sonnet 5 | $0.00008 | $0.00411 |
| Haiku 4.5 | $0.00004 | $0.00205 |
Grade A, and why
validation-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 4d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validation Microflows Skill
This skill provides guidance for creating validation microflows in MDL that validate user input on NewEdit pages and provide feedback to users.
When to Use This Skill
Use this skill when:
- Creating validation logic for NewEdit pages
- Implementing attribute validation with feedback messages
- Building conditional validation chains
- Creating action microflows that call validation microflows
Nanoflow validation: The same patterns apply to nanoflows (
create nanoflowinstead ofcreate microflow). Use nanoflows for client-side validation when server roundtrips are unnecessary — validation feedback renders instantly without a network call.
The Validation Pattern
Mendix validation follows a two-microflow pattern:
-
VAL_Entity_Action - The validation microflow that:
- Takes an entity object as parameter
- Validates each required field
- Shows validation feedback on invalid fields
- Returns a Boolean indicating overall validity
-
ACT_Entity_Action - The action microflow that:
- Calls the validation microflow
- Only proceeds with save/commit if validation passes
- Closes the page on success
MDL Syntax
VALIDATION FEEDBACK Statement
validation feedback $VariableName/attributename message 'Error message';
With template arguments (for dynamic messages):
validation feedback $VariableName/attributename message '{1}' objects [$MessageVariable];
CLOSE PAGE Statement
close page;
Or to close multiple pages:
close page 2;
Complete Example
Validation Microflow (VAL_Car_NewEdit)
/**
* Validates a Car entity for NewEdit operations
*
* Performs validation on all required fields and displays
* appropriate error messages to the user.
*
* @param $Car The Car entity to validate
* @returns Boolean indicating if all validations passed
*/
create microflow MdlTemplates.VAL_Car_NewEdit (
$Car: MdlTemplates.Car
)
returns boolean as $IsValid
folder 'OverviewPages'
begin
-- Initialize validation flag
declare $IsValid boolean = true;
-- Validate Brand (required text field)
if trim($Car/Brand) = '' then
set $IsValid = false;
validation feedback $Car/Brand message 'Brand is required';
end if;
-- Validate Model (required text field)
if trim($Car/model) = '' then
set $IsValid = false;
validation feedback $Car/model message 'Model is required';
end if;
-- Validate Price (required, must be positive)
if $Car/Price = empty then
set $IsValid = false;
validation feedback $Car/Price message 'Price is required';
else
if $Car/Price <= 0 then
set $IsValid = false;
validation feedback $Car/Price message 'Price must be greater than 0';
end if;
end if;
-- Validate enumeration (required)
if $Car/CarType = empty then
set $IsValid = false;
validation feedback $Car/CarType message 'Car type is required';
end if;
return $IsValid;
end;
/
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.
- 4d ago First seen · 292 lines · 38 tokens per session scan A 1f19efa2fa51
validation-microflows is a skill published in the GitHub repository mendixlabs/mxcli (116 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 2,055 once invoked, about $0.0002 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.