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/odata-data-sharingnpx skills add mendixlabs/mxcli --skill odata-data-sharinggit 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.00054 | $0.02804 |
| Opus 5 | $0.00027 | $0.01402 |
| Sonnet 5 | $0.00011 | $0.00561 |
| Haiku 4.5 | $0.00005 | $0.00280 |
Grade A, and why
odata-data-sharing 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OData Data Sharing Between Mendix Apps
This skill covers how to use OData services to share data between Mendix applications, with emphasis on using view entities as an abstraction layer to decouple the API contract from the internal domain model.
Reference files
SKILL.md covers the architecture, the contract rules, and the conventions. The
long build-outs are next door:
reference/walkthroughs.md— four complete builds, start to finish: a read-only API behind view entities, a non-persistable published entity, a read-write API with microflow handlers, publishing a microflow as an OData action, and the GraphQL variant.reference/errors-and-auth.md— which HTTP status each capability can actually return, the authentication methods and what Basic auth costs, and the configuration microflow for custom headers.
When to Use This Skill
- User asks to expose data from one Mendix app to another
- User wants to set up inter-app communication via OData
- User needs to create an API layer that abstracts internal entities
- User asks about external entities, consumed/published OData services
- User wants to decouple modules or apps for independent deployment
- User asks about the view entity pattern for OData services
- User asks about local metadata files or offline OData development
MetadataUrl Formats
CREATE ODATA CLIENT supports three formats for the MetadataUrl parameter:
| Format | Example | Stored In Model |
|---|---|---|
| HTTP(S) URL | https://api.example.com/odata/v4/$metadata |
Unchanged |
| Absolute file:// URI | file:///Users/team/contracts/service.xml |
Unchanged |
| Relative path | ./metadata/service.xml or metadata/service.xml |
Normalized to absolute file:// |
Path Normalization:
- Relative paths (with or without
./) are automatically converted to absolutefile://URLs in the Mendix model - This ensures Studio Pro can properly detect local file vs HTTP metadata sources (radio button in UI)
- Example:
./metadata/service.xml→file:///absolute/path/to/project/metadata/service.xml
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 · 305 lines · 54 tokens per session scan A a604f960bdbd
odata-data-sharing is a skill published in the GitHub repository mendixlabs/mxcli (115 stars, last pushed 2d ago), licensed Apache-2.0. It adds 54 tokens to every session and 2,804 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
zh-output-example
Reviews Chinese skill documentation for publication readiness. Invoke when the user asks in Chinese to review a skill.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
powerpoint
Create designed, editable PowerPoint .pptx presentations with PptxGenJS. Use when the user asks to create, generate, update, or inspect a deck, slide deck, presentation, or .pptx file.
review-offered-task
Review a task that has been offered to you and decide whether to accept or reject it.
Swift Performance Optimization Skill
Use when investigating measured Swift or Apple-platform regressions in CPU, memory, launch, scrolling, animation hitches, image processing, energy, networking, or concurrency, or when designing performance tests and Instruments experiments. Do not use for speculative micro-optimization, ordinary refactoring, or a…
systematic-debugging
Root-cause a bug already in front of you, instead of guessing at fixes. Use on triggers like "root cause this", "why is this failing", "debug systematically", "this test is flaky", "it works locally but not in CI", or when a fix attempt has already failed once. Enforces a phased evidence-first process before any code…