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/fix-issue)<a href="https://agentmods.dev/commands/mendixlabs/mxcli/fix-issue"><img src="https://agentmods.dev/badge/commands/mendixlabs/mxcli/fix-issue/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/fix-issue"><img src="https://agentmods.dev/badge/commands/mendixlabs/mxcli/fix-issue.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.00016 | $0.01087 |
| Opus 5.5 | $0.00006 | $0.00435 |
| Sonnet 5.5 | $0.00003 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
fix-issue 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 7d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mxcli-dev:fix-issue — Fix a Reported Bug
Work a bug report end to end: match it against what has already been seen, fix it, and prove the fix with evidence a reviewer can check.
Read .claude/skills/fix-issue.md first — it holds the
findings-lookup mechanics and the two rules that are easiest to skip. This command
is the order to do things in.
$ARGUMENTS is the issue number or a description of the symptom.
Steps
-
Read the issue in full, including comments. Quote the reported symptom verbatim somewhere — it is what the test has to reproduce, and paraphrasing it is how a fix ends up addressing a different bug.
-
Match the failure class, then the instance:
docs-wiki/bug-patterns/for the class (small, read it)grep -ril '<CE code or keyword>' .claude/skills/fix-issue/findings/for the instance
A pattern-page miss means "not yet digested", never "not seen before".
-
Establish the version facts before theorising, if the report involves one. The arbiter for a metamodel property is the Mendix Model SDK's own
StructureVersionInfo(npm pack mendixmodelsdk, then grepsrc/gen/*.jsfor the type) — not release notes, and not a number already written down in this repo. mendixlabs/mxcli#1121 was a floor copied from a proposal's illustrative sample output that nobody had ever measured. -
Write the failing test first, at the layer the symptom lives in. Table of layer → package is in the skill.
-
Prove the test detects the bug. Revert the fix, or stub the guard, and confirm it fails with the reported symptom. Put the control's output in the PR. A test that has only ever run against fixed code has not been shown to detect anything.
-
Run the real thing when the argument calls for it. Required when the fix's justification asserts what a Mendix tool accepts or rejects — a version guard, a refusal, anything resting on "mxbuild would catch this". Also when the symptom is a property of the running app (
verify-in-runtime.md). Cheapest form:
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.
- 7d ago Changed 0e64b4171360
- 28d ago First seen · 89 lines · 16 tokens per session scan A abc04ac5c0df
fix-issue is a command published in the GitHub repository mendixlabs/mxcli (130 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 1,087 once invoked, about $0.0001 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-09-18.
Other commands, from other repositories
hatch3r-codebase-map
Reverse-engineer a brownfield codebase into current-state module boundaries, integration-point inventory, tech-debt register, and dependency graph via static analysis.
hatch3r-debug
Standalone debug-and-fix workflow — add strategic debug logging, collect runtime logs from the user, perform root cause analysis, implement the fix, and clean up all debug artifacts.
hatch3r-quick-change
Lightweight workflow for small changes not tracked on the board: adaptive ceremony, inline or sub-agent implementation, batch support.
hatch3r-bug-plan
Diagnose a complex incident -- reproduce the symptom, rank root-cause hypotheses, design the fix path, and emit regression coverage items as a board-ready investigation.
hatch3r-bug-pipeline
Run a known-cause bug fix through a 3-phase test-first pipeline -- reproduce + root-cause, regression-test + fix together, then root-cause-depth review -- with full sub-agent delegation.
hatch3r-diagnose
Troubleshoot a hatch3r framework issue (setup, config, adapter wiring, drift). Gathers state, delegates root-cause analysis to hatch3r-researcher, proposes a fix, and applies it via hatch3r-fixer after one confirmation gate.