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 skills add mendixlabs/mxcli --skill debug-microflowsgit 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/skills/mendixlabs/mxcli/debug-microflows)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/debug-microflows"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/debug-microflows/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/skills/mendixlabs/mxcli/debug-microflows"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/debug-microflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.02201 |
| Opus 5.5 | $0.00023 | $0.00880 |
| Sonnet 5.5 | $0.00011 | $0.00440 |
| Haiku 4.5 | $0.00006 | $0.00220 |
Grade A, and why
debug-microflows 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 5d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find it fast
sed -n '<from>,<to>p' SKILL.md one section rather than reading the file;
./mxcli syntax <topic> answers how do I write this for a fraction of either.
| lines | section |
|---|---|
| 26-37 | Overview |
| 38-47 | When to use this skill |
| 48-61 | Prerequisites |
| 62-81 | The loop |
| 82-101 | Commands |
| 102-132 | Nanoflows (client-side) |
| 133-149 | Gotchas |
| 150-157 | Validation checklist |
| 158-160 | Microflow/nanoflow debugger (mxcli debug) |
Debug Microflows — mxcli debug
Overview
mxcli debug drives the Mendix runtime's microflow debugger from the command
line: set breakpoints by name, inspect a paused microflow's variables, and
step/continue — against an app started by mxcli run --local. It is the headless
counterpart to Studio Pro's debugger, so you can debug a server-side microflow
without leaving the warm loop.
mxcli is uniquely able to offer breakpoints by name because it owns both
halves: the admin password + app URL (from run --local) and the activity model
GUIDs (from the .mpr). You never deal with raw GUIDs.
When to use this skill
- A page action throws or misbehaves and you need to see where in a microflow it goes wrong, with the in-scope variables.
- You want to confirm a microflow takes the branch/value you expect.
For a server stack trace / LOG output (not stepping), you usually just want
the runtime log — see run-local (--runtime-log). Use the debugger when you
need to pause and inspect live execution.
Prerequisites
-
The app running under
mxcli run --local(Mendix 11.x). -
Start it with
--debugso the debugger is enabled and a session is ready:mxcli run --local -p app.mpr --debug--debugalone does not change runtime behaviour — nothing pauses until you set a breakpoint. It caches a debug session token under<projectDir>/.mxcli/so themxcli debugcommands below (run from another terminal, same-p) work immediately, with no separatemxcli debug enable.
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.
- 5d ago Changed · +18 lines 746fb79d50b3
- 23d ago Changed · +4 lines 4ef660c16e11
- 1mo ago First seen · 139 lines · 57 tokens per session scan A be00b36de6a7
debug-microflows is a skill published in the GitHub repository mendixlabs/mxcli (130 stars, last pushed yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 2,201 once invoked, about $0.0002 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 skills, from other repositories
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
memory-leak-debug
Diagnose memory leaks in the Qwen Code CLI using heap snapshots and the chrome-devtools CLI. Use when investigating high memory usage, unbounded growth, or suspected object retention issues.
bugfix
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.