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 manage-securitygit 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/manage-security)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/manage-security"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/manage-security/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/manage-security"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/manage-security.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.00052 | $0.06613 |
| Opus 5.5 | $0.00021 | $0.02645 |
| Sonnet 5.5 | $0.00010 | $0.01323 |
| Haiku 4.5 | $0.00005 | $0.00661 |
Grade A, and why
manage-security 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 yesterday.
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 — 641 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 |
|---|---|
| 27-35 | When to Use This Skill |
| 36-43 | Security Concepts |
| 44-120 | The System-module ceiling — decide the role model around this FIRST |
| 121-552 | Syntax Reference |
| 553-567 | Starlark Lint Rule APIs |
| 568-620 | Common Workflow: Setting Up Module Security |
| 621-630 | Common Mistakes |
| 631-640 | Validation |
Security Management Skill
This skill covers Mendix security configuration via MDL: module roles, user roles, access control (microflows, pages, entities), project security settings, and demo users.
When to Use This Skill
Use when the user asks to:
- Set up security for a module or project
- Create or manage module roles / user roles
- Grant or revoke access to microflows, pages, or entities
- Configure project security level or demo users
- Review existing security configuration
Security Concepts
- Module Roles define permissions within a single module (e.g.,
Shop.Admin,Shop.Viewer) - User Roles aggregate module roles from multiple modules (e.g.,
AdministratorincludesShop.Admin+System.Administrator) - Access Rules control CRUD rights on entities per module role
- Microflow/Page Access controls which module roles can execute/view specific elements
- Project Security Level determines enforcement:
off,prototype, orproduction
The System-module ceiling — decide the role model around this FIRST
No project module can widen access to System.User, System.Workflow or
System.WorkflowUserTask. Access to System entities comes from the System
module's own roles, and a grant in your module cannot raise it. This is a design
constraint, not a detail: it decides what your screens can be, and finding it late
means rebuilding them (ako/mxcli-maintenance-2 designed a technician picker, built
it, tested it, and tore it out).
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.
- yesterday Changed · +6 lines bba21cd8877f
- 2d ago Changed · -4 lines 97afa3a0f161
- 4d ago Changed · +10 lines 5c48dafc960a
- 5d ago Changed · +17 lines b7a7265fbff9
- 8d ago Changed · +4 lines 5ed8390a00d8
- 13d ago Changed · +27 lines f4f41ef1fee9
- 15d ago Changed · +18 lines 05ff379b239f
- 16d ago Changed · +21 lines 418a6bfe41ac
- 24d ago Changed · +36 lines c7350ffad24b
- 1mo ago First seen · 506 lines · 52 tokens per session scan A 85a5d57aaddf
manage-security is a skill published in the GitHub repository mendixlabs/mxcli (131 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 6,613 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
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.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
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…
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop.
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
workflow-creator
Create or update reusable Dynamic Workflow JavaScript files under .qwen/workflows. Use when the user asks to create, save, edit, or reuse a Dynamic Workflow, including requests started from the Web Shell Workflows page.