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 agentmods add skills/mendixlabs/mxcli/live-edit-with-studio-pronpx skills add mendixlabs/mxcli --skill live-edit-with-studio-progit clone --depth 1 https://github.com/mendixlabs/mxcliWhat 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 | $0.00050 | $0.01273 |
| Opus 5 | $0.00025 | $0.00636 |
| Sonnet 5 | $0.00010 | $0.00255 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
live-edit-with-studio-pro 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Live-Editing an Open Studio Pro Project with mxcli (MCP)
Use mxcli to change the model while Studio Pro has the project open, with edits appearing live in Studio Pro — no save-and-reopen cycle. This is the workflow when Claude Code runs on the same machine as Studio Pro (e.g. an in-IDE terminal).
When to use this skill
- Studio Pro is open on the project and you want mxcli changes to show up live.
- mxcli and Studio Pro run on the same machine (same
localhost).
If Studio Pro is not open, use the normal file-based flow instead
(mxcli -p app.mpr -c "..." with no --mcp), which edits the .mpr on disk.
How it works (hybrid: local reads, live writes)
- Reads come from the local
.mpryou pass with-p. - Writes go to Studio Pro's live, in-memory model via its built-in MCP server.
- Therefore
-pMUST be the exact project Studio Pro currently has open, or reads and writes will describe different projects.
Connect
Studio Pro's MCP server listens on localhost:7782 and requires the HTTP
Host header to be localhost (a DNS-rebinding guard). Same-machine, no
port-forwarding/socat is needed:
mxcli --mcp http://localhost/mcp --mcp-dial localhost:7782 \
-p /path/to/app.mpr \
-c "create entity MyModule.Customer"
--mcp-dial localhost:7782 keeps the Host header localhost while dialing the
port. (Plain --mcp http://localhost:7782/mcp may also work if your Studio Pro
accepts a port-suffixed Host — try it; fall back to the --mcp-dial form if it
is rejected.)
Run a script the same way: mxcli --mcp http://localhost/mcp --mcp-dial localhost:7782 -p app.mpr exec changes.mdl.
What you can change via MCP — check first
What's authorable over MCP depends on the Studio Pro version and on this session. The capability surface changes per release, but it also depends on your Studio Pro preferences (some tools are togglable) and on which MCP servers you have connected to Studio Pro. So the answer is not derivable from a version number — ask the connected server, every session, before generating MDL:
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 First seen · 107 lines · 50 tokens per session scan A 9b9e757119e4
live-edit-with-studio-pro is a skill published in the GitHub repository mendixlabs/mxcli (115 stars, last pushed 3d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,273 once invoked, about $0.0003 per session on Opus 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
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
pr-feedback
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.
Swift Performance Optimization Skill
Use when investigating measured Swift or Apple-platform regressions in CPU, memory, launch, scrolling, animation hitches, image processing, energy, networking, or concurrency, or when designing performance tests and Instruments experiments. Do not use for speculative micro-optimization, ordinary refactoring, or a…
asc
Drive App Store Connect from the terminal with the asc CLI — TestFlight builds, groups, testers and What to Test notes; App Store versions, metadata, keywords, screenshots and release notes; submissions and review health; signing, provisioning and notarization; crash and beta-feedback triage; pricing, subscriptions…
doubt-driven-review
In-flight adversarial check on a non-trivial decision BEFORE it stands — distinct from post-hoc review of a finished diff. Use on "stress-test this decision", "are we sure about this", "verify before commit", "poke holes in this", when working in unfamiliar code, or before an irreversible step (migration, prod deploy…