Universal Modder: Install and Test Your First Mod

Universal Modder gives AI coding agents modding skills, game research notes and an optional um command-line program. It helps an agent inspect a game you own, choose a game-specific route, make a small change and verify it. It does not turn any two game names into a finished mashup in one step.

Official source: Universal Modder on GitHub (opens in a new tab). Source checked: October 19, 2026. This is a guide to the creator's documented workflow, not a claim that GameMerging AI built and tested a mod on your PC.

Before you install

Choose one locally installed game you own and one small change you can recognize in-game. A new block in a supported Minecraft setup or one new weapon in a documented game is a smaller first target than connecting two running games.
Back up the game's saves and record its exact version. Work in a separate folder. Do not use an online game with anti-cheat for an unapproved modding experiment.
Install and open one supported coding agent. The creator lists Claude Code, Codex and other agents. For the command-line tools and many game workflows, the README lists Git, Python 3.10+ and FFmpeg; game-specific loaders and SDKs are separate requirements.
A fal API key is for optional generated assets. It is not required merely to inspect a game or plan a code-only first change. Coding-agent subscriptions, original games and optional asset services have separate costs.

Need help choosing between a guided mashup platform and direct mod development? Read How to Combine Games with AI.

Install for your coding agent

Choose the route for the agent you actually use. Run Codex commands in a terminal. Run Claude Code slash commands inside Claude Code.

Codex plugin:

codex plugin marketplace add rehan-remade/universal-modder
codex plugin add universal-modder@universal-modder

Claude Code plugin:

/plugin marketplace add rehan-remade/universal-modder
/plugin install universal-modder@universal-modder

Expected result: The chosen agent lists the installed Universal Modder plugin or can see its skills. If the plugin command fails, read the exact agent error and compare your agent's current plugin support with the creator's installation table (opens in a new tab). Do not paste the Claude Code commands into a terminal or install both routes without using both agents.

Install and check the separate `um` CLI

The creator's current README says the Claude Code plugin places um on PATH. A Codex, Cursor or Gemini plugin installation does not by itself put um on the terminal PATH. If you want to run um directly, install it once using the creator's Python package route:

uv tool install git+https://github.com/rehan-remade/universal-modder

The README also lists pipx install git+https://github.com/rehan-remade/universal-modder as an alternative; use one package manager, not both. In the same terminal where you plan to work, check:

um --help
um scan --help

Expected result: Both help commands print the available commands and options. If um is not recognized, check that Python, uv or pipx is installed and that the tool directory is on this terminal's PATH. A missing terminal command does not prove the agent plugin failed. The current README explains PATH differences for each agent.

Build one small, reversible test

Identify the game. Record its installed edition, version, engine and whether it already has a documented mod loader. If your um CLI works, use um scan --help to choose the scan syntax for your version and um kb search "GAME NAME" to look for prior field notes. Check: the agent names your real installation and a plausible route. If not: provide the game folder and version; do not invent a loader.
Ask for a plan before code. Give the agent the exact behavior you want and a single test action. Check: it returns the files it would change, required dependencies, save backup and rollback steps. If not: reduce the goal to one action in one game.
Build through the game's own route. Let the agent follow the relevant loader or SDK documentation. There is no universal compile command for every game. Check: the mod package builds and the base game still starts. If not: stop and save the first actual compiler or loader error.
Verify in the running game. Perform the one planned action and record what happened, plus the game and mod versions. Check: a visible change occurs and you can repeat it. If not: use the logs and changed-file list to debug or revert; do not call an unfinished file a playable mashup.

Copy and adapt this first-task brief for your own game. The bracketed fields are for you to fill in:

I own [GAME] version [VERSION] on [PLATFORM].
I want one small offline change: [ONE MECHANIC].
First inspect the game, its engine, existing mod loader and prior notes.
Do not edit game files or saves until you show me a plan.
List the exact files and tools needed, one in-game test that proves success,
the logs to capture if it fails, and how to undo every change.
Stop after the first working slice. Do not claim two games are connected
unless you have demonstrated that connection in a running build.

This is a planning prompt, not a tested download or a guarantee that the specified game supports the requested mod. The creator's Minecraft inside GTA V example (opens in a new tab) shows how much more work a two-process crossover can require.

Troubleshooting by symptom

Symptom	Check and next action
Agent cannot see the skills	Confirm you used the install route for that agent and read its plugin output. Open the current README installation table (opens in a new tab) before repeating commands.
Terminal says `um` is not recognized	Check whether the CLI was installed separately and whether this terminal has the tool directory on PATH. `um --help` is the verification point.
Game scan does not find the installation	Compare the actual game folder and edition with the agent's report. Use `um scan --help` for current syntax; give the folder path to the agent if discovery fails.
A Windows GTA build script prints `' "" ' is not recognized`	In creator Issue #88 (opens in a new tab), the author traced this specific message to missing Visual Studio C++ x64 tools. Install Visual Studio 2022 or Build Tools with Desktop development with C++, or set `VCVARS` to the correct `vcvars64.bat` as the author describes. This is a diagnosis for that script, not a universal fix for all build errors.
The agent returns unfinished files or runs out of credits	Preserve the last error and ask for one smaller feature. The creator's response to Issue #28 (opens in a new tab) explains that a full Minecraft-in-Elden-Ring bridge can take multiple days; the repository does not ship that ready-made mod.
The mod builds but does not load	Match the game, loader and mod versions; capture the loader or game log and restore the backup if startup fails. Do not disable security software or anti-cheat as a generic fix.

What counts as a first success?

Your base game starts; the chosen loader reports the mod; the one planned action produces a visible result; and you can identify and revert the files changed. A generated image, code draft or successful compilation alone is not proof of an in-game feature.

Sources: Creator README (opens in a new tab), Issue #88 (opens in a new tab), Issue #28 (opens in a new tab). Checked October 19, 2026.

Next: How to Combine Games with AI · Explore Real Mashups