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 teamserver-gitgit 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/teamserver-git)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/teamserver-git"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/teamserver-git/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/teamserver-git"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/teamserver-git.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00108 | $0.01722 |
| Opus 5.5 | $0.00043 | $0.00689 |
| Sonnet 5.5 | $0.00022 | $0.00344 |
| Haiku 4.5 | $0.00011 | $0.00172 |
Grade A, and why
teamserver-git 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 4d 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 — 127 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 |
|---|---|
| 35-41 | The rule: let Studio Pro do version control when it can |
| 42-55 | Branches: create them on the server |
| 56-78 | Commit from the agent |
| 79-93 | Push the branch and the notes together, and soon |
| 94-106 | Never rewrite or merge model history with git |
| 107-117 | Reading what Studio Pro recorded |
| 118-126 | Checklist |
Working with Git on a Mendix Team Server Project
A Mendix project in git is more than its files. Studio Pro keeps four things in step that plain git does not, and a commit that skips them makes Studio Pro report conflicts nobody can see, crash on open, or refuse to deploy a revision.
| What | Where | What breaks without it |
|---|---|---|
| Model units | mprcontents/**/*.mxunit |
— (git handles these) |
| Unit index | the .mpr Unit table, ContentsHash per unit |
Studio Pro's change detection; it shows changes the files do not have |
| Commit metadata | a git note per commit under refs/notes/mx_metadata |
version check and package build for that revision; the history shows (unknown) |
| Branches | on the Team Server | Studio Pro 11.13 crashes opening a branch that has no upstream |
The rule: let Studio Pro do version control when it can
If the user has the project open in Studio Pro, the cheapest correct commit is theirs: Version Control › Commit in Studio Pro commits, writes the note, and pushes, all in one go, even when every change in it was made with mxcli. Suggest that first. Everything below is for committing from the agent.
Branches: create them on the server
- Never
git checkout -ba branch the user will open in Studio Pro. A local-only branch has no upstream, and Studio Pro 11.13 fails to open it with "Unable to find 'system' property in 'system'". - Ask the user to create the branch in Studio Pro: Version Control › Manage
Branch Lines… › New. That creates it on the Team Server. Then
git fetch && git switch <branch>, and git tracks it asorigin/<branch>. - If they want the agent to do it instead, it must be pushed with an upstream
straight away. That is an outward action, so ask first:
git switch -c <branch> && git push -u origin <branch>. mxcli docker check,mxcli run --localandmxcli diag -p app.mprwarn when the checked-out branch has no upstream.
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.
- 4d ago Changed · +16 lines 9eb5d5db3a94
- 7d ago First seen · 111 lines · 108 tokens per session scan A 3d7423125d9b
teamserver-git is a skill published in the GitHub repository mendixlabs/mxcli (130 stars, last pushed yesterday), licensed Apache-2.0. It adds 108 tokens to every session and 1,722 once invoked, about $0.0004 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-10-09.
Other skills, from other repositories
conventional-commit
Conventional Commit - Generate Conventional Commits 1.0.0 compliant messages. MANDATORY for all git commits. Invoke when user says 'commit', 'commit this', or asks to commit code.
git-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…
pr-writer
Writes a pull-request description from the actual diff.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
docs-update-from-diff
Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.