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 write-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/write-microflows)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/write-microflows"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/write-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/write-microflows"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/write-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.00049 | $0.07686 |
| Opus 5.5 | $0.00020 | $0.03074 |
| Sonnet 5.5 | $0.00010 | $0.01537 |
| Haiku 4.5 | $0.00005 | $0.00769 |
Grade A, and why
write-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 2d 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 — 728 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 |
|---|---|
| 34-51 | Reference files |
| 52-61 | When to Use This Skill |
| 62-76 | Changing an Existing Microflow |
| 77-95 | When to Use a Microflow vs a Nanoflow |
| 96-112 | Key Differences from Nanoflows |
| 113-267 | Microflow Structure |
| 268-345 | Variable Declarations |
| 346-403 | Operators |
| 404-420 | Logging |
| 421-446 | Special Values |
| 447-493 | Complete Example |
| 494-550 | Calling Microflows |
| 551-578 | Page Navigation |
| 579-595 | Validation Checklist |
| 596-607 | Tips for Success |
| 608-614 | Related Documentation |
| 615-727 | Quick Reference |
Mendix Microflow Skill
Reference files
SKILL.md covers the shape of a microflow and the decisions. The detail lives beside it:
reference/control-flow.md— every form ofif,case,split type,loopandwhile, plus error handling (try/custom handlers) and the@position/@merge/@anchoractivity annotations.reference/data-operations.md— create, change, commit, delete; list operations and aggregates;retrievefrom database, association and list; XPath navigation.reference/integration.md—rest callandsend rest request, legacy SOAP, calling Java actions (including theemptyargument and microflow-typed parameters),execute database query, file downloads.reference/pitfalls.md— read this whenmxcli checkrejects something you believe is correct. The anti-patterns, the CE0111 duplicate-variable trap, the syntax that looks plausible and does not parse, and the Studio Pro errors each one produces.
When to Use This Skill
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · +2 lines 97778cbe4cf4
- 3d ago Changed · -2 lines 00012da313ca
- 4d ago Changed 5b26a63f0be0
- 9d ago Changed cd29180fc71b
- 13d ago Changed 8c6ffeef2943
- 14d ago Changed 73c3a3fa3473
- 15d ago Changed · +27 lines 53bd8ff3e1a5
- 19d ago Changed 808ef149212a
- 23d ago Changed 92204ab8a91b
- 25d ago First seen · 701 lines · 49 tokens per session scan A 89e848a52a71
write-microflows is a skill published in the GitHub repository mendixlabs/mxcli (132 stars, last pushed 2d ago), licensed Apache-2.0. It adds 49 tokens to every session and 7,686 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-09-03.
Other skills, from other repositories
golang-manual-di
Guides manual dependency injection wiring for Go services: three-tier naming taxonomy (Provide/MustProvide/Must), Must-pattern entrypoints, OS-signal-driven context lifecycle, common provider structs, infrastructure must-builders, interface-segregated bus registration, decorator/tracing wrappers, and…
terraform-infrastructure
Structures, writes, and reviews Terraform infrastructure code. Covers module layout, remote state, workspace strategy, variable and secrets handling, CI plan/apply pipeline, naming conventions, and multi-region deployment patterns (provider aliases, per-region state, failover strategies), while delegating shared risk…
microservices-architecture
Guides service boundary analysis, communication pattern selection, data consistency design, API contract strategy, and resilience checklist for microservices systems. Complements the microservices fragment. Invoked when the user asks to design a microservices system, split a monolith, or review service boundaries.
nosql-database-design
Designs a NoSQL data model by leading with access pattern analysis. Covers DynamoDB single-table design (PK/SK/GSI) and MongoDB embedding vs referencing, consistency models, and capacity planning. Invoked when the user asks to design a DynamoDB schema, MongoDB data model, or NoSQL data model.
health-check-endpoints
Implements liveness and readiness health check endpoints following Kubernetes probe conventions. Covers response schema, dependency checks, Kubernetes probe config, and circuit breaker integration. Invoked when the user asks to add health checks, implement a /health endpoint, or set up Kubernetes probes.
serverless-architecture
Designs and implements serverless functions: function boundary design, runtime selection, event sources, IAM least privilege, configuration, observability, and cost estimation. Invoked when the user asks to build a serverless function, design a Lambda-based system, or move workloads to serverless.