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.
git 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/commands/mendixlabs/mxcli/diff-script)<a href="https://agentmods.dev/commands/mendixlabs/mxcli/diff-script"><img src="https://agentmods.dev/badge/commands/mendixlabs/mxcli/diff-script/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/commands/mendixlabs/mxcli/diff-script"><img src="https://agentmods.dev/badge/commands/mendixlabs/mxcli/diff-script.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00010 | $0.00802 |
| Opus 5.5 | $0.00004 | $0.00321 |
| Sonnet 5.5 | $0.00002 | $0.00160 |
| Haiku 4.5 | $0.00001 | $0.00080 |
Grade A, and why
diff-script 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 14d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diff Script
Compare an MDL script against the current state of a Mendix project to see what would change.
Commands
# Unified diff (default) - traditional +/- format
mxcli diff -p app.mpr changes.mdl
# Side-by-side comparison
mxcli diff -p app.mpr changes.mdl --format side
# Structural summary
mxcli diff -p app.mpr changes.mdl --format struct
# With color output
mxcli diff -p app.mpr changes.mdl --color
# Side-by-side with custom width
mxcli diff -p app.mpr changes.mdl --format side --width 140
Output Formats
Unified (default)
Traditional diff format showing + for additions and - for removals:
--- Entity.MyModule.Customer (current)
+++ Entity.MyModule.Customer (script)
@@ -1,5 +1,6 @@
CREATE PERSISTENT ENTITY MyModule.Customer (
Name: String(100) NOT NULL,
- Email: String(200)
+ Email: String(200) NOT NULL,
+ Phone: String(20)
);
Side-by-Side (--format side)
Two-column comparison showing current vs proposed:
Entity.MyModule.Customer
──────────────────────────────────────────────────────────────────
Current │ Script
──────────────────────────────────────────────────────────────────
Email: String(200) │ Email: String(200) NOT NULL, ~
│ Phone: String(20) +
Structural (--format struct)
Summary of changes by element type:
Entity: MyModule.Customer
~ Attribute Email: changed
+ Attribute Phone: String(20)
Entity: MyModule.Order
+ New
What Gets Compared
mxcli diff runs the script with exec's own code on a scratch copy of the
project, then compares the copy with the project unit by unit. It reports
exactly the units exec would write — every document kind (domain model per
entity and association, pages, snippets, layouts, flows, security, navigation,
settings, folders) and every statement kind — each shown as its describe
before and after. The project itself is not changed.
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.
- 14d ago Changed · +8 lines b6aadbd954f1
- 16d ago Changed · +7 lines 604d9b631b41
- 1mo ago First seen · 101 lines · 10 tokens per session scan A bccb2fbba88d
diff-script is a command published in the GitHub repository mendixlabs/mxcli (131 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 802 once invoked, about $0.0000 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 commands, from other repositories
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.
hatch3r-release
Release-workflow orchestrator — preflight, SemVer bump, changelog sync, build + CycloneDX SBOM, adapter-output verification, quality gates, release-notes reconciliation, then stop before publish/merge for human approval.
archive
Finalize a completed change — sync specs when needed, then archive it.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
commit.zh-CN
A command for creating a Git commit, which is a saved checkpoint of changes in a Git project.
post-release.en
Read and execute the post-release skill from .agents/skills/post-release/SKILL.md.