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 json-structures-and-mappingsgit 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/json-structures-and-mappings)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/json-structures-and-mappings"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/json-structures-and-mappings/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/json-structures-and-mappings"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/json-structures-and-mappings.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.05959 |
| Opus 5.5 | $0.00021 | $0.02384 |
| Sonnet 5.5 | $0.00011 | $0.01192 |
| Haiku 4.5 | $0.00005 | $0.00596 |
Grade A, and why
json-structures-and-mappings 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 — 717 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 |
|---|---|
| 33-110 | Key Concepts |
| 111-122 | Export Mappings |
| 123-187 | JSON Structures |
| 188-229 | Message Definitions |
| 230-393 | Import Mappings |
| 394-491 | Export Mappings |
| 492-509 | Starting a Mapping Below the Payload Root |
| 510-593 | Microflow Actions |
| 594-606 | Browse |
| 607-654 | Export Workflow: PE → NPE → JSON |
| 655-661 | Realistic Example: Countries REST API |
| 662-685 | Placing Documents in Folders |
| 686-701 | Documentation |
| 702-716 | Common Mistakes |
JSON Structures, Import Mappings & Export Mappings
This skill covers creating and managing JSON structures, import mappings, and export mappings in Mendix using MDL.
Key Concepts
JSON Structures
A JSON structure defines the schema of a JSON payload. It stores a JSON snippet and auto-derives an element tree with paths, types, and custom names.
Import Mappings
An import mapping converts a JSON string into Mendix entity objects. It maps JSON fields to entity attributes.
Two names per member: the raw key and the exposed name
Every JSON structure element stores both, and for any lowercase-initial key they differ:
| Example | Used for | |
|---|---|---|
| Path (raw JSON key) | (Object)|uuid |
what the runtime resolves by |
| ExposedName (derived) | Uuid |
what Studio Pro displays |
Mendix derives the exposed name by capitalising the initial, and for an array's
item object by suffixing Item — so total → Total, camelCase → CamelCase,
__Value (array) → __ValueItem (its item). Keys already starting with an
underscore are left alone: __returnedCount stays __returnedCount.
This is Mendix's own convention, not something mxcli does. A blank app's
Studio-Pro-authored FeedbackModule.JSON_AppInsightsResponse stores
ExposedName: "Uuid" against Path: "(Object)|uuid", and its IMM_PostResponse
binds JsonPath: "(Object)|uuid".
What ships with it
3 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 Changed · +17 lines dec827ea35f9
- 5d ago Changed · +17 lines c0df7ed9aa71
- 15d ago Changed · +22 lines e7cfde501a2d
- 18d ago Changed · +3 lines 34f886934ef5
- 21d ago Changed · +16 lines 203fbd321406
- 24d ago Changed · +4 lines 17fa508cfa79
- 25d ago Changed · +8 lines cdb67f5e052c
- 26d ago Changed 005612c3c6c1
- 1mo ago Changed · +3 lines 4966c36127cd
- 1mo ago First seen · 627 lines · 53 tokens per session scan A efa4d61a905e
json-structures-and-mappings is a skill published in the GitHub repository mendixlabs/mxcli (132 stars, last pushed 2d ago), licensed Apache-2.0. It adds 53 tokens to every session and 5,959 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-08-30.
Other skills, from other repositories
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.
health-check-endpoints
Implements liveness and readiness health check endpoints following Kubernetes probe conventions. Covers response schema, dependency checks, Kubernetes probe config, and circuit breaker integration. Invoked when the user asks to add health checks, implement a /health endpoint, or set up Kubernetes probes.
serverless-architecture
Designs and implements serverless functions: function boundary design, runtime selection, event sources, IAM least privilege, configuration, observability, and cost estimation. Invoked when the user asks to build a serverless function, design a Lambda-based system, or move workloads to serverless.