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/proposalgit 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.00012 | $0.01317 |
| Opus 5 | $0.00006 | $0.00659 |
| Sonnet 5 | $0.00002 | $0.00263 |
| Haiku 4.5 | $0.00001 | $0.00132 |
Grade A, and why
proposal 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mxcli-dev:proposal — Create Feature Proposal
Guide the contributor through creating a well-structured feature proposal for
mxcli. The proposal goes in docs/11-proposals/PROPOSAL_<name>.md.
Process
Work through these phases interactively — ask the user questions, don't guess. Each phase produces concrete output.
Phase 1: Understand the Feature
Ask the user:
- What do you want to add? (one sentence)
- Why — what problem does this solve, or what user story does it enable?
- Which Mendix version introduced this capability? (affects version-gating)
- Does this add MDL syntax? (CREATE/ALTER/DROP/SHOW/DESCRIBE statements)
- Does this touch BSON serialization? (reading or writing Mendix documents)
If the user isn't sure about version or BSON, help them find out:
- Version: check
reference/mendixmodellib/reflection-data/or Mendix release notes - BSON: check if similar features exist in
sdk/mpr/parser*.goorsdk/mpr/writer*.go
Phase 2: BSON Investigation (if applicable)
CRITICAL: If the feature reads or writes Mendix documents, investigate the BSON structure BEFORE designing syntax. Wrong assumptions here cause CE errors in Studio Pro that are painful to debug.
-
Find a working example — ask the user:
- "Do you have a test
.mprproject with this feature already configured in Studio Pro?" - If yes: use
mxcli bson dumpormxcli bson discoverto extract the BSON structure - If no: ask them to create a minimal example in Studio Pro first
- "Do you have a test
-
Extract the BSON structure:
# Find the document type ./bin/mxcli -p project.mpr -c "SHOW STRUCTURE ALL" | grep -i <feature-name> # Dump the raw BSON ./bin/mxcli bson dump -p project.mpr --type "<BSON $Type>" # Or discover all instances of a type ./bin/mxcli bson discover -p project.mpr --pattern "<pattern>" -
Document the BSON structure in the proposal:
- Storage name (
$Typefield) — verify againstreference/mendixmodellib/reflection-data/ - All fields with types and observed values
- Any fields that use Mendix-internal IDs (pointers to other documents)
- Note any counter-intuitive naming (like Parent/Child pointer inversion)
- Storage name (
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 · 165 lines · 12 tokens per session scan A 2a3e39e29d06
proposal is a command published in the GitHub repository mendixlabs/mxcli (115 stars, last pushed 2d ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,317 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.