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 system-modulegit 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/system-module)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/system-module"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/system-module/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/system-module"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/system-module.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.00053 | $0.04352 |
| Opus 5.5 | $0.00021 | $0.01741 |
| Sonnet 5.5 | $0.00011 | $0.00870 |
| Haiku 4.5 | $0.00005 | $0.00435 |
Grade A, and why
system-module 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 — 540 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 |
|---|---|
| 32-49 | Access to System entities has a ceiling |
| 50-56 | Reference files |
| 57-66 | When to Use This Skill |
| 67-127 | How to Reference System Entities |
| 128-220 | 1. User Management & Authentication |
| 221-274 | 2. File Management |
| 275-332 | 3. HTTP / Web Services |
| 333-359 | 4. Error Handling |
| 360-383 | 7. Utility Entities |
| 384-448 | 8. Enumerations |
| 449-480 | 9. Inheritance Hierarchies |
| 481-536 | 10. Common Patterns |
| 537-539 | Source |
Mendix System Module Reference
The System module is a built-in Mendix module present in every application. It provides core entities for user management, file handling, workflows, task queues, HTTP services, and more. These entities are not defined in the application's domain model but are available for use in microflows, pages, associations, and Java actions.
Access to System entities has a ceiling
No project module can widen access to System.User, System.Workflow or
System.WorkflowUserTask. Their access comes from the System module's own roles,
and a grant in your module cannot raise it — so any UI over them is
Administrator-only unless the data is denormalised into entities your own module owns.
A microflow data source is not the way out. It moves the ROWS, not the MEMBERS: the retrieve is unconstrained, but the runtime re-applies entity access when it serializes those objects to the client, so the list is the right length and every field is blank (measured on 11.14.0, ako/mxcli#587). Read the members inside the microflow and return an object your module owns.
It fails silently: a combo box over System.User lists the current user only, a
grid over System.Workflow renders empty, and mx check, mxcli lint and
mxcli report all pass. See the System-module ceiling section in
manage-security for the measurement and the remedies.
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.
- 5d ago Changed · +22 lines 1e4cdbae9191
- 15d ago Changed · +7 lines db603fe3e5a6
- 16d ago Changed d3ac47aa1106
- 24d ago Changed · +5 lines c5f66a293f88
- 29d ago Changed · +25 lines 7bca2d3a8042
- 1mo ago Changed f2f453e8e23f
- 1mo ago First seen · 481 lines · 53 tokens per session scan A b1c029930f1a
system-module is a skill published in the GitHub repository mendixlabs/mxcli (131 stars, last pushed yesterday), licensed Apache-2.0. It adds 53 tokens to every session and 4,352 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.