Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mendixlabs/mxclinpx agentmods add commands/mendixlabs/mxcli/proposalWrote 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/proposal)<a href="https://agentmods.dev/commands/mendixlabs/mxcli/proposal"><img src="https://agentmods.dev/badge/commands/mendixlabs/mxcli/proposal/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/proposal"><img src="https://agentmods.dev/badge/commands/mendixlabs/mxcli/proposal.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.00012 | $0.01395 |
| Opus 5.5 | $0.00005 | $0.00558 |
| Sonnet 5.5 | $0.00002 | $0.00279 |
| Haiku 4.5 | $0.00001 | $0.00139 |
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 6d 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 — 169 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/list/describe statements, or a microflow/nanoflow activity)
- 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 the Mendix release notes
- BSON: check if similar features exist in
mdl/backend/modelsdk/*_read.goor*_write.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 againstmodelsdk/gen/<domain>/types.goand the dumped document - 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.
- 6d ago Changed 9b1f167cc8c7
- 9d ago Changed · +4 lines 3ce9b55d1f28
- 28d ago Changed b23dab17a9ac
- 1mo ago First seen · 165 lines · 12 tokens per session scan A 2a3e39e29d06
proposal is a command published in the GitHub repository mendixlabs/mxcli (130 stars, last pushed today), licensed Apache-2.0. It adds 12 tokens to every session and 1,395 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-workflow
Guided development lifecycle with 4 phases (Analyze, Plan, Implement, Review) and scale-adaptive Quick Mode for small tasks; --plan-file executes an approved plan document without re-deriving it.
hatch3r-roadmap
Sequence delivery phases over time into a dependency-ordered milestone plan with business and technical lenses, emitting a todo.md rollout schedule rather than design docs.
hatch3r-migration-plan
Create a phased migration plan for a major dependency or framework upgrade. Analyzes breaking changes and produces an actionable plan with rollback procedures.
hatch3r-incident-response
Drive a live production incident through a structured lifecycle -- triage + topology, bounded-autonomy mitigation, stakeholder communication, then a blameless post-mortem with runbook -- via delegated sub-agents.
hatch3r-slo-scaffold
Generate baseline SLI/SLO scaffolding for a user-facing service — availability + latency p95/p99 objectives, 28-day error budget, and Google-SRE multi-window multi-burn-rate alert rules in OpenSLO openslo/v1. Implementer writes the files; hatch3r-reliability gates them against the CQ4 floor.
hatch3r-pack-install
Walk the user through the pack trust-model gate (tier + signature + body-scan + capability declaration), confirm the trust posture, then delegate the verified install to hatch3r-pack-installer.