Install Universal Modder without guessing
Choose your agent route for Universal Modder. The Claude Code plugin puts um on PATH; Codex, Gemini CLI, Cursor and OpenCode plugin installs need a one-time um CLI install.
Check prerequisites
Install Git, Python 3.10+ and ffmpeg; uv is recommended for the Python toolkit. Node.js and npx are needed if you choose skills-only installation. Blender is needed only for 3D-to-sprite rendering.
Record your agent and operating-system versions. Windows game automation runs natively on Windows or from WSL; a successful toolkit install on another OS does not prove that a Windows game can be driven there.
Choose a separate mod working folder. You do not need to buy asset credits or provide a fal key to begin checking installation and planning a small code change.
Choose the installation route for your agent
Open the matching agent instructions below. Run terminal commands in your shell and Claude Code slash commands inside Claude Code. Review the source before installing third-party code.
These routes follow the pinned upstream README. Plugin and extension support depends on your installed agent release; the local-clone or skills-only route provides a fallback when the documented integration is unavailable.
Claude Code
Add the project marketplace, then install its plugin. These slash commands belong in a Claude Code session, not in your operating-system shell.
/plugin marketplace add rehan-remade/universal-modder
/plugin install universal-modder@universal-modderCheck the result: Confirm the plugin is listed in Claude Code. Open a terminal in the same environment and run um --help. A listed plugin and a help menu do not show that fal is connected.
If this route is unavailable: If your agent release does not support this plugin route, use the local-clone route below.
Codex CLI
Use the plugin commands documented by the upstream project. Check codex plugin --help first; plugin availability depends on your installed Codex release.
codex plugin marketplace add rehan-remade/universal-modder
codex plugin add universal-modder@universal-modderCheck the result: Check codex plugin list to confirm the plugin. The upstream README says Codex plugin installs do not put um on PATH, so install the CLI once (see the full installation instructions), then run um --help in a fresh Codex session in your separate mod working folder. Neither step tests fal.
If this route is unavailable: If the plugin subcommand is unavailable, start the agent inside a local clone or use skills-only installation. A CLI instruction is not a guarantee that the desktop app exposes the same controls.
Gemini CLI
Install the repository as a Gemini CLI extension, then start a fresh agent session in your mod working folder.
gemini extensions install https://github.com/rehan-remade/universal-modderCheck the result: Confirm the extension appears in gemini extensions list. The upstream README says Gemini CLI extension installs do not put um on PATH, so install the CLI once (see the full installation instructions), then check um --help in the environment Gemini uses. Neither step tests fal.
If this route is unavailable: If the extension command is unavailable in your release, use a local clone and check the current Gemini CLI documentation.
VS Code / GitHub Copilot
Enable chat.plugins.enabled in Settings. Open the Command Palette, run Chat: Install Plugin From Source, and enter https://github.com/rehan-remade/universal-modder.
Check the result: Confirm the plugin appears in the editor, then check um --help in the integrated terminal. The upstream README does not say whether this route puts um on PATH; if the command is not found, install the CLI once (see the full installation instructions). Copilot access and billing are separate from the open-source toolkit.
If this route is unavailable: If the setting or command is absent, your editor release may not support this route. Open a local clone instead and review its .vscode/mcp.json configuration.
Cursor
The README lists Cursor Marketplace as an option. The concrete fallback is to clone the repository and open that folder in Cursor, which reads AGENTS.md and .cursor/mcp.json.
git clone https://github.com/rehan-remade/universal-modder
cd universal-modderCheck the result: Open the cloned folder in Cursor and inspect its MCP configuration. In a clone, run export PATH="$PWD/bin:$PATH" from the repository root in the terminal you use (current shell only). A Marketplace plugin install does not add um, so use the one-time CLI install from the full installation instructions. Then run um --help.
If this route is unavailable: We have reviewed the repository instructions, not independently verified a live marketplace listing. Use the clone route if you cannot find the plugin.
OpenCode
Clone the repository and run OpenCode inside it. The repository includes opencode.json for its skills and fal MCP server.
git clone https://github.com/rehan-remade/universal-modder
cd universal-modder
opencodeCheck the result: Inspect the skills and MCP configuration loaded by your installed agent. In the clone, run export PATH="$PWD/bin:$PATH" from the repository root in the terminal you use (current shell only), then run um --help there. A loaded MCP configuration does not show that fal works.
If this route is unavailable: Cloning the repository does not install OpenCode itself. Verify your agent installation before investigating the modding toolkit.
Skills only / another compatible agent
Add the Agent Skills instructions, then install the um toolkit separately. Skills installation alone does not prove that the agent has a working CLI or fal MCP connection.
npx skills add https://github.com/rehan-remade/universal-modder
uv tool install git+https://github.com/rehan-remade/universal-modder
um --helpCheck the result: Confirm the skills appear in a location your agent reads, and that um --help prints its command menu. Neither step shows that fal is connected.
If this route is unavailable: For an agent without Agent Skills support, clone the repository and start the agent in that folder. Review the repository instructions before running any setup commands.
Verify the CLI in the agent’s environment
CLI availability depends on the integration, not just whether a plugin appears in your agent. The pinned README documents automatic PATH setup for the Claude Code plugin through its SessionStart hook, and for a clone opened in Claude Code through .claude/settings.json. With another agent in a local clone, run export PATH="$PWD/bin:$PATH" from the repository root before checking um --help in that terminal. This changes the current shell only.
Codex, Cursor, Gemini CLI and OpenCode plugin installs do not add um to PATH. Skills-only installation also requires a separate CLI install. For these routes, install the CLI once with the command below, then check um --help in the agent’s terminal. If uv lists the toolkit but the agent still cannot find it, compare the agent terminal with your normal shell.
uv tool install git+https://github.com/rehan-remade/universal-modder
um --help
uv tool list
uv tool dir --binConfigure assets only when needed
fal cloud asset generation is optional and uses FAL_KEY. Keep the key in your local environment, never in a public prompt, screenshot or repository. Restart the agent after changing its environment.
The CLI and the agent’s fal MCP connection are separate checks. A working um command does not prove MCP authentication works. Local ComfyUI is another image-generation route documented upstream, with its own setup requirements.
Before touching a game, confirm the skills, CLI and exact game path, then back up saves. A help menu verifies tool discovery; only a test in the actual game verifies a mod.
Compare version-sensitive instructions with the current upstream documentation. Source version: 9811709.
Upstream documentation ↗Asset connection failing? Check fal key and MCP setup →