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 regular-expressionsgit 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/regular-expressions)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/regular-expressions"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/regular-expressions/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/skills/mendixlabs/mxcli/regular-expressions"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/regular-expressions.svg" alt="Reviewed on agentmods" width="80" 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.00048 | $0.01778 |
| Opus 5.5 | $0.00019 | $0.00711 |
| Sonnet 5.5 | $0.00010 | $0.00356 |
| Haiku 4.5 | $0.00005 | $0.00178 |
Grade A, and why
regular-expressions 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 5d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find it fast
sed -n '<from>,<to>p' SKILL.md one section rather than reading the file;
./mxcli syntax <topic> answers how do I write this for a fraction of either.
| lines | section |
|---|---|
| 26-32 | When to Use This Skill |
| 33-58 | What a Mendix regular expression is |
| 59-68 | Writing the pattern |
| 69-83 | Go cannot check every legal pattern |
| 84-142 | Binding a regex to an attribute |
| 143-155 | Finding out who uses one |
| 156-167 | Common Mistakes |
| 168-173 | Related |
| 174-176 | Regular expressions (LIST/DESCRIBE/CREATE [OR MODIFY]/DROP REGULAR EXPRESSION) |
Regular Expressions
When to Use This Skill
Use this skill when the user wants to:
- Add a named validation pattern (email, phone, identifier, postcode)
- See or change the regexes a project already has
- Understand why a regex cannot be attached to an attribute from MDL
What a Mendix regular expression is
A document, not a string on a rule. An attribute validation rule stores a
reference to it by qualified name, so one pattern is shared by every attribute
that validates against it. That is why it gets a create statement of its own.
mdl 1;
list regular expressions;
list regular expressions in Val;
describe regular expression Val.EmailAddress; -- re-executable MDL
/** A, not too restrictive, email address regular expression */
create regular expression Val.EmailAddress (
Expression: '\w+((-|\+|\.)\w+)*@\w+([\.-]?\w+)*(\.\w{2,})+'
);
drop regular expression Val.EmailAddress;
| Property | Meaning | Default |
|---|---|---|
Expression |
the pattern — required | — |
Documentation |
free text | none |
ExportLevel |
Hidden or API (Public is a deprecated spelling of API, MDL-DEPR161) |
Hidden |
Writing the pattern
The pattern is an ordinary MDL string:
- Backslashes are NOT escape characters. Write
\d,\w,\.exactly as Mendix should see them — do not double them. - A single quote is doubled, like any MDL string:
'^it''s$'. - Commas, braces and pipes inside the pattern are fine — the whole thing is one quoted string.
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.
- 5d ago Changed · +18 lines df6ac4083ead
- 14d ago Changed 419dd890ae06
- 15d ago Changed · +4 lines fda53c765722
- 16d ago Changed 667e5281ad13
- 24d ago Changed · +4 lines f60436d6a4c5
- 1mo ago First seen · 151 lines · 48 tokens per session scan A 3ce01ce91379
regular-expressions is a skill published in the GitHub repository mendixlabs/mxcli (131 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 1,778 once invoked, about $0.0002 per session on Opus 5.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
hatch3r-api-spec
Generates and validates OpenAPI specifications from codebase. Covers endpoint design, schema validation, and documentation generation.
hatch3r-scalability-verify
Scalability verification gate before commit/release — stateless-handler ratio, back-pressure patterns, idempotency-key adoption, queue-based offloading, pool sizing, bulkheads, load-test pass at target scale.
golang-manual-di
Guides manual dependency injection wiring for Go services: three-tier naming taxonomy (Provide/MustProvide/Must), Must-pattern entrypoints, OS-signal-driven context lifecycle, common provider structs, infrastructure must-builders, interface-segregated bus registration, decorator/tracing wrappers, and…
terraform-infrastructure
Structures, writes, and reviews Terraform infrastructure code. Covers module layout, remote state, workspace strategy, variable and secrets handling, CI plan/apply pipeline, naming conventions, and multi-region deployment patterns (provider aliases, per-region state, failover strategies), while delegating shared risk…
microservices-architecture
Guides service boundary analysis, communication pattern selection, data consistency design, API contract strategy, and resilience checklist for microservices systems. Complements the microservices fragment. Invoked when the user asks to design a microservices system, split a monolith, or review service boundaries.
nosql-database-design
Designs a NoSQL data model by leading with access pattern analysis. Covers DynamoDB single-table design (PK/SK/GSI) and MongoDB embedding vs referencing, consistency models, and capacity planning. Invoked when the user asks to design a DynamoDB schema, MongoDB data model, or NoSQL data model.