unity-agent-plugin: Unity's skills packaged for four coding agents

One plugin, four agent platforms, and a skills folder underneath

unity-agent-plugin is Unity's official game development plugin, and the description says what it is for: build, monetize and operate Unity games with guidance grounded in Unity's documented practices. The interesting structural detail is that this is not a Unity Editor extension in the usual sense. It is a bundle of agent skills, and the same content is served to four different coding agents. The repository layout shows the mechanism: a `skills/` directory at the root holds the actual instructions, and there are four separate plugin manifests, `.claude-plugin/`, `.codex-plugin/`, `.antigravity-plugin/` and `.agents/`, each describing how that particular agent should discover and load the same skills. The primary language is listed as C#, which is what the skills talk the agent into writing.

Installing into Claude Code, Codex, Grok and Antigravity

The install section is one subsection per platform, and the differences are worth reading rather than skimming. For Claude Code there are two forms, because the slash commands have to be typed inside a session rather than in a terminal:

%s

and then:

%s

From a terminal, the `claude` CLI does the same thing:

%s

Codex uses `codex plugin marketplace add` followed by `codex plugin add`. Grok has a single command with a `--trust` flag:

%s

And Antigravity takes a repository URL:

%s

The README notes that installs done through the Claude Code CLI load the next time you start Claude Code, or when you run `/reload-plugins` in an open session, which is a small operational detail that catches people out.

The terminal form of the Claude Code install is a single block:

bash claude plugin marketplace add Unity-Technologies/unity-agent-plugin claude plugin install unity@unity-agent-plugin

Verifying the install, and what the version string tells you

Each agent surfaces an installed plugin differently, and the README covers all four. In Claude Code you type `/unity:` and the skills appear in the command list, and `/plugin` also shows `unity` as installed and enabled. In Codex you run `codex plugin list` and get a table:

%s

Grok uses the plain skill name in the slash menu and switches to the plugin-qualified form such as `/unity:ui-uitk` when another installed skill shares the same name. In Antigravity, `agy plugin list` gives:

%s

The version string in those outputs, 0.1.8-beta, is worth pausing on. There are no GitHub releases for this repository, so the plugin is versioned independently of the repository tags, and a beta version of a plugin that edits your project is a signal about how you should approach using it.

A manual install links the skills into your personal directory

If the marketplace commands are not an option, the README documents a manual route. You clone the repository and change into it:

%s

Then you link each skill into your personal skills directory. For Claude Code:

%s

And for Codex:

%s

The README explains the consequences of this path. The skills load in every project from your next session onward, and to update them you run `git pull` in the clone. It also notes a limitation that matters for anyone switching approaches: skills installed this way do not appear under a `unity:` prefix, because they are not installed as a plugin. So a manual install is functionally equivalent but visually different in the agent's command list.

The skills edit your project directly, and the README says to commit first

The Usage section opens with a warning that is the most important sentence in the file. The skills have your agent change your project directly. It edits scripts, scenes and assets, and when the Unity CLI is available it runs C# in your open Editor. Not every change is logged or can be undone from the Editor, so the README tells you to keep your project under version control and commit before asking for larger changes. That is an unusually direct statement of the failure mode, and it comes from the plugin author rather than from a third party. The examples given for what you can ask for are also concrete: add in-app purchases so players can buy a coin pack, build a settings screen, fix pixel art that looks blurry and jitters when the camera moves, show rewarded video ads, create a hexagonal tile palette, fix Chinese characters showing up as empty boxes in TextMeshPro labels, and review a ScriptableRendererFeature for Render Graph problems.

The Unity CLI is what makes the skills more than text

Many skills drive your open Unity Editor directly rather than hand-editing scene and asset files. They create GameObjects, change import settings, run C# in the Editor and check the result. All of that goes through the Unity CLI, Unity's command-line tool, which also installs Editors, creates and opens projects, and runs builds and tests. The setup burden is deliberately low, because when a task needs the CLI, the agent checks whether it is installed and can install it for you, along with the small Unity package the CLI uses to talk to your open Editor. If you use the Unity Hub you probably already have it, since the Hub now installs it automatically. The README states the requirement plainly: Unity 6+. The practical reading is that the difference between a skill that writes plausible code and a skill that verifies the result in the Editor is the CLI being present.

Where unity-agent-plugin is the wrong tool

Three limits are concrete. The first is that the skills act on your project without asking. The README's own warning covers this, and it is the reason a version of 0.1.8-beta should make you want your project in git with a clean working tree before every session. A tool that runs C# in your open Editor is a tool that can trigger a recompile, a domain reload and asset reimport in the middle of your work, and the README does not promise that every such change is logged or reversible. The second is the licensing. The repository is under the Unity Companion License, which the repository metadata reports as a custom licence GitHub cannot classify, and the README notes that Unity's branding and trademark guidelines apply to Unity marks and icons in the repo. If you are building a product and want to know what you can ship, that file is the one to read. The third is the scope: this is guidance for working inside Unity, not a general engine, a build pipeline or a test framework, and it has no meaning outside a Unity 6 or later project.

The alternative is writing the prompt yourself, or using the docs directly

The realistic alternative is to skip the plugin and either write your own prompt or point an agent at Unity's documentation. The difference in approach is who curates the knowledge. The plugin's value is that the skills encode the recommended way to do a task, so you get a workflow rather than an improvisation, and the README is explicit that the guidance is grounded in Unity's documented practices. A hand-written prompt gets you the same underlying documentation but leaves the sequencing to the model, and a model with the docs in context will sometimes write a C# script that compiles and does not work, because nothing in the prompt told it to create the object, check the result and adjust. The other alternative is the editor documentation and the manual approach, which is the most reliable option and the slowest. For a team already working in Unity daily, the plugin is a way to convert documentation knowledge into a repeatable workflow, at the cost of letting an agent write into your project.

Editorial conclusion

unity-agent-plugin fits a team already working in Unity 6 or later who wants an agent to follow Unity's documented practices instead of improvising, and who keeps the project in git with a clean tree before each session. It is the wrong choice if you need a stable release to pin, since the plugin reports itself as 0.1.8-beta with no GitHub releases, and the wrong choice if you cannot accept an agent that edits scenes and assets and runs C# in your open Editor. Before you install it, read the Unity Companion License in the repository, confirm your project is committed, and check that the Unity CLI is available, since the skills that verify their own results depend on it.

Frequently asked questions

Official sources

1. Issues
2. README
3. Unity-Technologies/unity-agent-plugin on GitHub