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 agentmods add skills/mendixlabs/mxcli/generate-domain-modelnpx skills add mendixlabs/mxcli --skill generate-domain-modelgit clone --depth 1 https://github.com/mendixlabs/mxcliWhat 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 | $0.00055 | $0.01722 |
| Opus 5 | $0.00028 | $0.00861 |
| Sonnet 5 | $0.00011 | $0.00344 |
| Haiku 4.5 | $0.00006 | $0.00172 |
Grade A, and why
generate-domain-model 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 yesterday.
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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Mendix Domain Model MDL Scripts
Use this skill to generate Mendix domain model scripts in MDL (Mendix Definition Language) format and validate them with the linter.
Reference files
SKILL.md covers the process and the decisions — what to model, in what order,
and how to check it. The lookup material is next door:
reference/syntax.md— the complete syntax for entities, attributes, associations and enumerations, every attribute type, plus reserved keywords and entity positioning. Check a spelling here rather than guessing; a reserved word used as an attribute name fails in Studio Pro, not in the parser.reference/patterns.md— the recurring domain shapes (header/detail, categorisation, audit, soft delete, many-to-many with payload) and a full worked e-commerce model.
When to Use This Skill
- User asks to create a domain model for a specific use case
- User wants to generate entities, associations, and enumerations
- User requests a complete e-commerce, HR, CRM, or other business domain model
- User needs validation of generated MDL scripts
Modelling for the client: widgets bind members, not expressions
A page widget binds an attribute or association path — never an expression. There
is no substring(attr, i, 1) or computed binding in a widget. So a value that must be
rendered per-part (each character of a code, each cell of a grid, each of N pencil
marks) has to be stored as separate attributes, not packed into one string and
indexed client-side. Model the wide form when the UI needs to address the parts
individually (e.g. N1…N9 booleans rather than a packed Notes string); reach for
a computed/derived value only where a microflow or view-entity OQL produces it into a
real attribute. (Same reason the bucket-class idiom exists — see
migrate-design-prototype.)
Documentation Best Practices
Entity Documentation
/**
* Brief one-line summary
*
* Detailed multi-line description explaining:
* - What the entity represents
* - Key business rules
* - Relationships to other entities
*
* @since 1.0.0
* @see Module.RelatedEntity
*/
What ships with it
2 files 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.
- yesterday First seen · 235 lines · 55 tokens per session scan A 1e6544eb60f9
generate-domain-model is a skill published in the GitHub repository mendixlabs/mxcli (115 stars, last pushed 2d ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,722 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-08-30.
Other skills, from other repositories
eliza-app-development
Use when building or changing an elizaOS-based application in this repository. Covers eliza app architecture, monorepo layout, local versus remote versus cloud routing, where to edit features, and non-negotiable runtime constraints. Eliza is the product name of this particular eliza app checkout.
live-verify
Two-part gate for gflow-cli feature/fix work. Part 1 (Pre-flight): use when starting work on a gflow-cli feature or fix — confirms the checkout reflects current develop before investing effort. Part 2 (Live-verify): use before claiming gflow-cli work done, especially anything touching a generation code path…
business-context
Maps a business type the user mentions (coffee shop, restaurant, e-commerce, clinic, gym, hotel, school and more) to its industry-standard feature set — POS, inventory, orders, booking, reports, staff — and auto-includes those features with no questions asked. Fuels zero-question planning for /toh-vibe and /toh-plan…
setup
Set up Mozaiks from scratch. Walks through Docker, Python, Node, environment variables, and verification.
pr
Open a pull request from the current worktree — verify green, commit scoped, push, and write the PR from the actual diff. Trigger on "/pr", "open a PR", "make a pull request".
payram-checkout-integration
Integrate PayRam checkout flow into web applications. Generate payment links, embed payment pages, handle redirects, and process payment confirmations. Supports Express, Next.js, FastAPI, Laravel, Gin, Spring Boot. Use when adding crypto checkout to e-commerce, building payment forms, implementing deposit flows, or…