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 commands/mendixlabs/mxcli/diff-scriptgit 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.00010 | $0.00585 |
| Opus 5 | $0.00005 | $0.00293 |
| Sonnet 5 | $0.00002 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00059 |
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 2d 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 — 101 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
- Entities: Attributes, constraints, indexes, documentation
- Enumerations: Values and captions
- Associations: Type, owner, delete behavior
- Microflows: Parameters, return type, body statements
Summary Output
Every diff ends with a summary:
Summary: 2 new, 3 modified, 5 unchanged
Use Cases
- Preview changes before executing a script
- Review modifications in a pull request
- Audit what an MDL script will modify
- Documentation of changes between versions
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.
- 2d ago First seen · 101 lines · 10 tokens per session scan A bccb2fbba88d
diff-script is a command published in the GitHub repository mendixlabs/mxcli (115 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 585 once invoked, about $0.0001 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 commands, from other repositories
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
plan
Create a structured task-by-task implementation plan for a feature and write it to docs/superpowers/plans/.
toh-help
Display all Toh Framework commands and quick usage guide.
specsmd-construction-agent
Command "specsmd-construction-agent" from fabriqaai/specs.md, covering activate construction agent, activation, parameters, critical first steps and your skills.
fire
FIRE orchestrator - Fast Intent-Run Engineering main entry point.
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.