Pick your coding agent, connect the tools you need, and start with one small change. Seven ways in. No account needed on this site.
Based on the original installation guideYou only need one installation path. Use the agent you already know.
An owned PC game, a backup of your saves, and the tools required for your chosen route.
Test with placeholder art. Add generated assets after the mod works.
Install through the plugin marketplace.
Inside a Claude Code session
/plugin marketplace add rehan-remade/universal-modder
/plugin install universal-modder@universal-modderRun each command in sequence. Claude Code access is separate from this free guide and may require a paid plan or API billing.
Use the plugin commands documented by the project.
In your terminal with a compatible Codex CLI
codex plugin marketplace add rehan-remade/universal-modder
codex plugin add universal-modder@universal-modderIf your installed CLI does not support plugins, use the clone route below. Agent access and usage limits are managed by your provider.
Add the repository as an extension.
In your terminal with Gemini CLI installed
gemini extensions install https://github.com/rehan-remade/universal-modderReview the extension permissions when prompted, then start a new session if the new skills are not visible.
Install from source using VS Code’s chat plugin support.
In VS Code settings and the Command Palette
This path needs a VS Code version with chat plugin support. Use the clone route if the setting or command is unavailable.
Use the marketplace, or open a local clone.
In Cursor
The clone route provides a concrete fallback if the marketplace listing is unavailable.
Bring the skill instructions into a compatible agent.
In your terminal with Node.js / npx available
npx skills add https://github.com/rehan-remade/universal-modderSkills are instructions. Check your agent’s MCP configuration and install the um CLI separately if needed; a skills-only install is not a complete local tool setup.
The fallback for agents that can read AGENTS.md.
In your terminal with Git installed
git clone https://github.com/rehan-remade/universal-modder
cd universal-modderStart your coding agent in this folder. Review AGENTS.md and approve only the local tool permissions you need.
The upstream setup lists Python 3.10+ and ffmpeg. uv is recommended. Your game’s loader may also need a language SDK or other game-specific tools.
You do not need these tools to browse this website or check a game.
A fal API key is for generating assets. Blender is for rendering 3D models into sprites. Neither is needed just to plan a mod or use your own placeholder art.
Claude access and fal asset generation may be billed separately by their providers.
The project documents this standalone CLI installation. Use it if your agent’s setup did not make the tool available.
uv tool install git+https://github.com/rehan-remade/universal-modderCheck that your terminal can find it:
um --helpCreate an API key in your fal dashboard, then set FAL_KEY in the environment that launches your agent. These examples set it for the current terminal session. Replace the placeholder locally.
macOS / Linux / WSL shell
export FAL_KEY="YOUR_FAL_API_KEY"Windows PowerShell
$env:FAL_KEY = "YOUR_FAL_API_KEY"Keep the key out of prompts, shared files, and source control. This website never asks for it.
Replace the game and idea below. Let the agent inspect the version, existing loaders, and field notes before it proposes changes.
Use universal-modder to help me mod my owned copy of Terraria in single-player. I want to add one simple item. Search the knowledge base, check my game and tModLoader versions, and explain the plan first. Back up my saves and use a separate test world. Ask before installing a loader or modifying game files. Start with placeholder art and verify the result in game.This site checks documented routes; it does not run mods. Use owned games and offline test profiles. Do not bypass anti-cheat, DRM, or ownership checks.
Find your gameUnofficial guide · universal-modder by rehan-remade, MIT · Reviewed October 4, 2026. Installation commands can change; check the upstream README if a command differs.