tutorial / first-session
Universal Modder tutorial: your first session, start to finish
Quick answer
One first session walks the full loop once: install the free plugin in your AI coding assistant, scan your game with um scan, snapshot your saves with um backup create, ask the agent for a MODDING_PLAN.md, build the smallest working slice, and verify it in the running game. The plugin and CLI are free; your assistant’s subscription is a separate paid plan, and AI-generated art is optional — your first mod can skip it entirely.
Watch a real creator run it
Third-party AI-news channel Theoretically Media put Universal Modder on camera and used it to put DOOM inside Skyrim in about an hour (English; the hands-on segment starts at 07:03):
It is a news-style segment rather than a full walkthrough — the steps below are the complete version.
Prerequisites
- An AI coding assistant with the universal-modder plugin installed — Claude Code, Codex, Cursor, Gemini CLI, VS Code or plain skills.
- Python 3.10+ available in your terminal;
uvis recommended. - A single-player PC game you legally own, with no anti-cheat protection.
- A separate working folder for mod projects, such as
C:\modsor~/mods.
Steps: the first-session loop
-
Install the plugin and start your agent in the mod folder
What to do
Install the plugin once per assistant, then start your agent inside the working folder. The example below uses Claude Code; the other agents follow the same plugin from their own install guides. Create the working folder first if it does not exist, then launch the agent from inside it.
Command
Command /plugin marketplace add rehan-remade/universal-modder /plugin install universal-modder@universal-modderWhat you should see
Claude Code confirms the marketplace was added and the plugin is installed. Choose the
Userscope when asked, so the plugin works in every folder. The plugin bundles the agent skills, the fal MCP tools and theumcommand line.If something goes wrong
If slash commands are not found after installing, run
/reload-plugins. For the other assistants, follow the matching guide: Codex, Cursor, Gemini CLI, VS Code, or skills-only setup. -
Scan the game you want to mod
What to do
From the same terminal (or ask the agent), scan the game.
um scanaccepts a fuzzy game name or an install folder;--listshows everything it found on Steam, Epic and Xbox. The scan reads files only — it does not change anything.Command
Command um scan --list um scan "Slay the Spire"What you should see
A report like the abridged example below: the install path, the engine with a confidence score, the anti-cheat check, installed loaders, save folders, and ranked modding routes.
Command Slay the Spire (steam 646570) path: ...\steamapps\common\SlayTheSpire engine: Java LibGDX [95%] evidence: desktop-1.0.jar anti-cheat: none found loaders: none installed saves: C:\Users\you\Documents\SlayTheSpire routes: 1. ModTheSpire base-mod hook (...)If something goes wrong
If the scan finds nothing, pass the install folder directly:
um scan "C:\...\steamapps\common\YourGame". If the report lists anti-cheat underanti-cheat:, stop — online-protected games are outside the boundary this project enforces. -
Back up your saves before anything changes
What to do
Snapshot the save folder that the scan printed on its
saves:line. Pass that exact folder path toum backup createand give the snapshot a name you will recognise later. This is the copy you can restore if a mod misbehaves.Command
Command um backup create "C:\Users\you\Documents\SlayTheSpire" --name before-first-modWhat you should see
One line confirming the snapshot: the output path followed by the number of files and total size, for example
... (17 files, 3.2 MB). Check it any time withum backup list before-first-mod.If something goes wrong
If a mod later corrupts the save, restore with
um backup restore before-first-mod --yes. Add--cleanto also delete files created after the snapshot. -
Ask the agent for a mod plan
What to do
Give the agent one small goal and ask for the plan before any code. The recon skill checks the knowledge base for prior field notes, fingerprints the route, and writes
MODDING_PLAN.md. Keep the goal small enough for one evening — one item, one mechanic.Command
Command Mod the game at "C:\...\steamapps\common\SlayTheSpire". First run um kb search for prior art on this game, then pick the safest route and write it to MODDING_PLAN.md. Do not change any files yet. My goal: add one custom relic that does something small and visible.What you should see
A
MODDING_PLAN.mdin your working folder describing the route, the files to touch, and the verification step — and no changes to the game folder yet.If something goes wrong
If the agent starts editing straight away, remind it: “Read the mod-any-game skill. Plan first, write MODDING_PLAN.md, wait for my OK.” The rules make it ask before driving your mouse, installing loaders or publishing.
-
Build the smallest working slice
What to do
Ask for the smallest change that proves the route works — one item, one stat change, one effect. Explicitly skip generated art for the first pass; placeholder art keeps the slice small and costs nothing.
Command
Command Follow MODDING_PLAN.md. Build only the first slice: the smallest change that loads in the real game. Use placeholder art, do not call fal yet. Back up saves first with um backup create if you have not already. When it builds, verify it in the running game and show me a screenshot.What you should see
The agent writes the mod code, builds it, and launches the game with the mod loaded. For code-only mods, no fal key and no paid generation is involved at any point.
If something goes wrong
If the slice grows out of control, ask the agent to re-read
MODDING_PLAN.mdand cut scope. If the game crashes, restore the save snapshot and ask the agent to read the crash report before retrying. -
Verify the mod in the running game
What to do
On Windows (or WSL), launch the game through
um winand take a screenshot of the game window to confirm the mod is live. On macOS or Linux, launch the game yourself and check the change visually.Command
Command um win launch "C:\...\SlayTheSpire.exe" um win shot "C:\mods\first-session.png"What you should see
The game window opens with the mod loaded, and
first-session.pngshows your change in the real game — that screenshot is your proof the whole loop worked.If something goes wrong
If
um win shotcannot find the window, pass--exe SlayTheSpire.exeor--title "Slay the Spire". To quit cleanly, close the game, then runum backup diff before-first-modto see exactly what the session changed on disk.
Verify it worked
um scanprints your game’s engine, ananti-cheatline, save folders and ranked routes.um backup list before-first-modshows the snapshot from step 3.MODDING_PLAN.mdexists in your working folder before any code was written.- The slice builds, the game launches with the mod, and your screenshot shows the change in-game.
um backup diffshows no changes inside the save folder itself.
FAQ
How long does a first Universal Modder session take?
Plan for one evening. The loop itself is short — scan, backup, plan, one slice, verify — and most time goes to the agent reading your game’s code and building the smallest slice. Keeping the first goal tiny is what keeps the session short.
Do I need a fal API key to follow this tutorial?
No. Code-only mods run entirely without a fal key, and this tutorial’s slice deliberately uses placeholder art. Add a fal key later only when you want the agent to generate sprites, 3D models or audio, which is a separate paid service.
What if the agent asks to drive my mouse or install a loader?
Those are normal parts of some routes, and the rules make the agent ask before driving input, installing loaders into game folders, changing the registry or publishing. Read the prompt, and decline anything you did not expect.
Can I follow this tutorial with any game?
With any single-player PC game you legally own that has no anti-cheat. The scan flags anti-cheat systems before anything happens, and the project refuses to inject into online-protected games — pick a different game if the report lists one.