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/lint)<a href="https://agentmods.dev/commands/mendixlabs/mxcli/lint"><img src="https://agentmods.dev/badge/commands/mendixlabs/mxcli/lint/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/lint"><img src="https://agentmods.dev/badge/commands/mendixlabs/mxcli/lint.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.01490 |
| Opus 5.5 | $0.00005 | $0.00596 |
| Sonnet 5.5 | $0.00002 | $0.00298 |
| Haiku 4.5 | $0.00001 | $0.00149 |
Grade A, and why
lint 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 3d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint Project
Check a Mendix project for common issues like naming convention violations, security gaps, and best practice deviations.
Commands
# Basic lint
mxcli lint -p app.mpr
# With colored output
mxcli lint -p app.mpr --color
# JSON output
mxcli lint -p app.mpr --format json
# SARIF output (for CI/GitHub)
mxcli lint -p app.mpr --format sarif > results.sarif
# List available rules
mxcli lint -p app.mpr --list-rules
# Exclude modules
mxcli lint -p app.mpr --exclude System --exclude Administration
Built-in Go Rules
| Rule | Category | Description |
|---|---|---|
| MPR001 | naming | NamingConvention - PascalCase with 21 microflow prefixes (ACT_, SUB_, DS_, VAL_, SCH_, IVK_, BCO_, ACO_, etc.) |
| MPR002 | quality | EmptyMicroflow - Microflows should have at least one activity |
| MPR003 | design | DomainModelSize - Max persistent entities per domain model |
| MPR004 | quality | ValidationFeedback - Validation feedback with empty message |
| MPR005 | quality | ImageSource - IMAGE widgets with no source configured |
| MPR006 | quality | EmptyContainer - Empty layout containers |
| MPR007 | security | PageNavigationSecurity - Navigation pages need allowed roles (CE0557); every user role must be able to open its home page (at Production security, else CE2729 per widget) |
| MPR012 | correctness | LegacyImageWidget - staticimage/dynamicimage are unsupported by the React client (CE0582) |
| SEC001 | security | NoEntityAccessRules - Persistent entities need access rules |
| SEC002 | security | WeakPasswordPolicy - Password minimum length should be 8+ |
| SEC003 | security | DemoUsersActive - Demo users should be off at Production security |
| SEC010 | security | PageEntityNotReadable - A page data widget lists an entity the user roles that open the page cannot read; at Production it renders empty, silently (info when only row-scoped) |
| CONV011 | performance | NoCommitInLoop - Commits inside loops (commit actions, or create/change with commit) cause N+1 issues |
| CONV012 | quality | ExclusiveSplitCaption - Exclusive splits need meaningful captions |
| CONV013 | quality | ErrorHandlingOnCalls - External calls (REST/WS/Java) need custom error handling |
| CONV014 | quality | NoContinueErrorHandling - Don't silently swallow errors with Continue |
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.
- 3d ago Changed · +1 lines a293be47b0b9
- 4d ago Changed 064cd433a052
- 5d ago Changed 8076742d3ece
- 8d ago Changed 201cdb70c703
- 24d ago Changed · +1 lines 2ea3ccdda66a
- 1mo ago First seen · 135 lines · 12 tokens per session scan A 69fd3254c8d2
lint 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,490 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-rework
User-guided rework planning for agent-implemented code in a fresh context window. Reconstructs what was delivered from the git diff, interviews the user for feedback, triages findings, validates them read-only against the code, and ends at a rework plan (docs/rework/) plus an execute-now-or-defer choice (copy-paste…
hatch3r-benchmark
Run and analyze performance benchmarks. Compare results against baselines, identify regressions, and produce performance reports.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.
code-review-give
Give mode for code-review: Review someone else's code with multi-pass analysis and structured recommendations.
mach12:issue-review
Read a GitHub issue and all comments, review the implementation plan, and present findings.