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 ProAnima/unity-version-control-mcp --skill uvcs-version-controlgit clone --depth 1 https://github.com/ProAnima/unity-version-control-mcpWrote 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/proanima/unity-version-control-mcp/uvcs-version-control)<a href="https://agentmods.dev/skills/proanima/unity-version-control-mcp/uvcs-version-control"><img src="https://agentmods.dev/badge/skills/proanima/unity-version-control-mcp/uvcs-version-control/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/proanima/unity-version-control-mcp/uvcs-version-control"><img src="https://agentmods.dev/badge/skills/proanima/unity-version-control-mcp/uvcs-version-control.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.00101 | $0.02333 |
| Opus 5.5 | $0.00040 | $0.00933 |
| Sonnet 5.5 | $0.00020 | $0.00467 |
| Haiku 4.5 | $0.00010 | $0.00233 |
Grade A, and why
uvcs-version-control 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 3d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Version Control (Plastic SCM) with the uvcs MCP server
This skill teaches you to answer source-control questions and perform source-control operations in a Plastic SCM / Unity Version Control (UVCS) workspace through the uvcs_* MCP tools. The tools wrap a fixed allowlist of cm commands. There is no shell access and no raw cm.
UVCS is not Git. Do not run git in a UVCS workspace, and do not describe UVCS concepts in Git terms without saying so: a changeset (cs:123) is a commit, a label (lb:NAME) is a tag, a branch is a path such as /main/task-42, a shelve (sh:12) is a stash kept on the server, and checkin is commit plus push in one step.
1. Check that the tools are available
Look for tools named uvcs_setup_status, uvcs_workspace_status, and so on (some clients prefix them, for example mcp__uvcs__uvcs_setup_status).
- If no
uvcs_*tools exist, stop and tell the user that the uvcs MCP server is not connected. Point them to the setup steps in references/setup.md. Do not edit MCP client configuration files yourself. - If a tool named in this skill is missing (for example
uvcs_merge_preview), the server is older than this skill. Use the closest available tool and suggest upgrading the server.
2. Orient yourself before anything else
- Call
uvcs_setup_status. Note the workspace path, repository, safety profile (readonly,guarded, orstandard), whether writes are enabled, the checkin file limit, and the naming rules. - Call
uvcs_branch_infoto learn the current branch and changeset. - In fleet mode every tool requires a
workspaceargument (a name from the fleet manifest). Pass it on every call and never mix workspaces in one operation.
If the profile is readonly, you can investigate and plan but not write. When the user wants a write, tell the user that writes are disabled and that enabling the guarded profile is their decision.
3. Pick the right tool
| The user wants | Call |
|---|---|
| What is modified in my workspace | uvcs_pending_changes, then uvcs_diff_file for a single file |
| What changed in changeset 123 / on a branch / between two builds | uvcs_changeset_diff (source: "cs:123", source: "/main/task", or source: "lb:A", compareTo: "lb:B") |
| The actual line changes of a file in that change | uvcs_revision_diff (changeset: "cs:123", or from/to) |
| Who changed a file and when | uvcs_file_history |
| Who wrote a specific line | uvcs_annotate with startLine / maxLines |
| Find a branch or label | uvcs_branch_list, uvcs_label_list |
| Recent activity by person, branch, or date | uvcs_changeset_analytics |
| Would this merge conflict | uvcs_merge_preview |
| Is it safe to switch, merge, or release | uvcs_branch_safety_report |
Unity .meta problems |
uvcs_unity_meta_diagnostics |
| Who holds a lock | uvcs_locks (pass paths to check specific files) |
| Lock a scene, prefab, or other binary asset before editing | uvcs_checkout_prepare / _confirm |
| Give back locks of files that were not changed | uvcs_release_checkout_prepare / _confirm |
| Check in only some files | uvcs_checkin_prepare with paths |
| Branch, checkin, or release names | uvcs_style_rules, uvcs_name_preview, uvcs_release_plan |
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.
- 3d ago First seen · 110 lines · 101 tokens per session scan A c3f5e2c1dae0
uvcs-version-control is a skill published in the GitHub repository ProAnima/unity-version-control-mcp (17 stars, last pushed 3d ago), licensed MIT. It adds 101 tokens to every session and 2,333 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-27.
Other skills, from other repositories
github-openapi-skill
Operate GitHub REST API through UXC with the official OpenAPI schema, explicit gh-to-uxc auth import, and read-first guardrails for repo, issue, pull request, and event workflows.
github
Generated by Gutenberg. Use this skill to call the github API through the local github CLI.
code-review
Systematic code review SOP covering correctness, security, performance, and maintainability — plus GitHub PR review workflow (diff, inline comments, approve via gh/REST).
git-workflow
Professional Git branching, commit, and PR workflow following conventional commits.
diff-summary
Structured triage of a git diff. One call replaces the per-file Read sweep an agent normally does to figure out which files in a diff are tests, which touch the public API, which are migrations, which need careful review.
github-pr-workflow
GitHub PR yaşam döngüsü — branch, commit, aç, CI izle, merge et.