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-navigationgit 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-navigation)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/manage-navigation"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/manage-navigation/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-navigation"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/manage-navigation.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.00050 | $0.06697 |
| Opus 5.5 | $0.00020 | $0.02679 |
| Sonnet 5.5 | $0.00010 | $0.01339 |
| Haiku 4.5 | $0.00005 | $0.00670 |
Grade A, and why
manage-navigation 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 — 598 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 |
|---|---|
| 31-40 | When to Use This Skill |
| 41-59 | Navigation Concepts |
| 60-77 | Show Commands (Read-Only) |
| 78-358 | CREATE OR MODIFY NAVIGATION (Full Replacement) |
| 359-380 | Round-Trip Workflow |
| 381-402 | Catalog Queries |
| 403-452 | Common Patterns |
| 453-504 | Menu Documents (standalone, reusable) |
| 505-575 | Offline Profiles |
| 576-590 | Checklist |
| 591-594 | Offline synchronization (CREATE NAVIGATION … SYNC (…)) |
| 595-597 | Menu documents (CREATE OR MODIFY/DESCRIBE/DROP MENU) |
Navigation Management Skill
This skill covers inspecting and modifying Mendix navigation profiles via MDL: home pages, menu items, login pages, role-based routing, and navigation catalog queries.
When to Use This Skill
Use when the user asks to:
- View or change navigation home pages
- View or modify the navigation menu structure
- Set login or not-found pages
- Configure role-based home page routing
- Discover which pages are navigation entry points
- Set up navigation for a new project
Navigation Concepts
-
Navigation Profiles — Every Mendix project has navigation profiles: Responsive, Phone, Tablet, and optionally Native. Each profile has its own home page, menu, and login page. The web kinds are a closed set and
create or replace navigationwill create one that does not exist yet:Online Offline twin ResponsiveResponsiveOfflinePhonePhoneOfflineTabletTabletOfflineAn invented name (
Mobile,Desktop) is an error, not a new profile: Mendix routes on User-Agent to its own kinds, so a profile the platform does not define can never be reached. Native profiles are a different document type and are not creatable from MDL. -
Offline Profiles — An offline profile makes the app work without a connection (a PWA with a local database that syncs). It is not a different document — same properties as its online twin — but it constrains every page it can reach, see below.
-
Home Page — The default page shown after login. Can be a PAGE or MICROFLOW.
-
Role-Based Home Pages — Override the default home page per user role (e.g., admins see a dashboard, users see a task list).
-
Menu Items — Hierarchical menu tree. Each item has a caption and optionally targets a PAGE or MICROFLOW. Sub-menus nest with
menu 'caption' { ... }. -
Menu Documents — A separate document type (
Menus$MenuDocument) holding a reusable menu that a menu widget points at, e.g. Atlas_Core'sPhone_Menu. Not the same thing as a profile's menu, though both are built from the same items, so the item syntax is identical. Managed withcreate/describe/drop menu— see below. -
Login Page — Custom login page (optional; Mendix provides a default).
-
Not-Found Page — Custom 404 page (optional).
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 · +21 lines 52412c9360d8
- 5d ago Changed · +21 lines cd3cfe1f84f5
- 12d ago Changed · +16 lines 5c6d4b9ade21
- 15d ago Changed · +14 lines 950342b1001f
- 16d ago Changed · +9 lines 99f3115b1acd
- 24d ago Changed · +8 lines 68fcf14037fb
- 1mo ago Changed · -2 lines 395ee6b06dee
- 1mo ago Changed · +32 lines 4b4edc38c1ec
- 1mo ago Changed · +67 lines d7a752efcee9
- 1mo ago First seen · 412 lines · 50 tokens per session scan A 98137e9622a3
manage-navigation is a skill published in the GitHub repository mendixlabs/mxcli (131 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 6,697 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.