Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Skills

Universal Modder — mod a PC game you own with an agent

Written November 1, 2026

github.com/rehan-remade/universal-modder · game-modding skills, a um command-line toolkit, and a shared knowledge base · MIT licence

What it does

Universal Modder is a set of skills, tools, and a shared knowledge base that let an AI coding agent mod a PC game the reader owns. The agent starts with the mod-any-game skill and runs the same loop every time: search the knowledge base, recon the game and pick a route, set up a safe lab with saves backed up, read the actual code, build one working slice, generate assets, test the result in the running game, record what was learned, package the mod, and write a field note for the next agent. The repository's own description of the loop is ten steps: search, recon, lab, source of truth, vertical slice, assets, in-game verification, record, package, field note.

The collection holds 13 skills. mod-any-game runs the loop. game-recon works out how a specific installed game can be modded and writes a modding plan. reverse-engineering reads how a game works with decompilers, debuggers, and memory tools. fal-assets and asset-pipeline generate and shape art, sound, and 3D models. port-a-mod moves an existing mod to a newer game version or another loader. publish-mod packages and releases a finished mod. game-automation launches and drives the real game so the agent can test its own work, and showcase-video cuts the demo clip. share-field-notes and game-research-websearch cover the knowledge base and web research, and two specialist skills cover mashup mods and Blitz3D decompilation. Sixteen engine reference files sit under the mod-any-game skill, covering Unity, Unreal, Godot, Source, Bethesda, Minecraft, .NET and XNA, Age of Empires II, Bannerlord, and native engines among others. The knowledge base holds field notes from agents that modded specific games, each giving the exact versions that worked, the route, how the result was tested in the game, and the gotchas.

The um command-line toolkit does the mechanical work: um scan finds installed games and fingerprints engine, runtime, anti-cheat, loaders, and save folders; um kb searches and writes field notes; um fal, um comfy, um sprite, and um render3d generate and shape assets; um backup snapshots save folders before they are touched; um publish lints a mod folder before sharing; and um fastfile, um iwi, and um weapon work with Call of Duty 4 and World at War files. Generated assets need a fal API key, and two sprite services, Sprixen and Voidless, are separate paid services with their own keys, per the repository's install notes.

The limits come first

Universal Modder's own safety rules draw a bright line, and it is the first thing to read before starting. Only single-player or offline games, or servers the reader runs themselves. Injecting into an online client breaks its terms and gets accounts banned, and writing cheats that give an advantage over other players — aimbots, wallhacks, speed hacks, recoil scripts, packet manipulation — is refused whatever the framing. Kernel or user-mode anti-cheat is a stop sign for code injection: EasyAntiCheat and BattlEye are named. The rules forbid disabling or bypassing anti-cheat, and forbid tampering with DRM or ownership checks. Mod only games the reader owns, from their own install or dumps of cartridges and discs they own. When a game's EULA or mod policy matters, the safety file says to read it, and says none of its own text is legal advice. No blanket statement that modding a named game is allowed appears in the repository's rules, and none appears here: the game's own terms decide.

Sharing has its own rules, enforced by the publish lint. No game files, no extracted assets, no ROMs or ISOs, and no links to pirated copies. No decompiled code dumps: describe the logic in the reader's own words and name symbols. No leaked material: no pasted code, attached files, download links, or licence keys from beta builds or leaked SDKs, and no instructions to fetch them. No secrets in a shared mod: API keys, tokens, and .env files fail the lint. The publish skill's lint fails a mod folder on files byte-identical to game files, leaked keys, and .env files, and warns on decompiler fingerprints in source.

Install

Universal Modder needs Git, Python 3.10 or newer, and ffmpeg. The uv tool is recommended. Blender is needed for 3D-to-sprite renders. Pick the install route for the agent in use; each route gets the same skills, the fal MCP server, and the um CLI:

Claude Code:  /plugin marketplace add rehan-remade/universal-modder
              /plugin install universal-modder@universal-modder
Codex:        codex plugin marketplace add rehan-remade/universal-modder
              codex plugin add universal-modder@universal-modder
Gemini CLI:   gemini extensions install https://github.com/rehan-remade/universal-modder
Skills only:  npx skills add https://github.com/rehan-remade/universal-modder
Anything else: git clone https://github.com/rehan-remade/universal-modder
              and start the agent inside the clone

For VS Code and Copilot, enable chat.plugins.enabled, run Chat: Install Plugin From Source, and enter the repository URL. For Cursor, use the Cursor Marketplace, or clone the repository; Cursor reads AGENTS.md and .cursor/mcp.json. For OpenCode, clone and run opencode inside the repository, or on OpenCode 2 add the plugin from the repository path the README names. Inside a clone, each agent finds the skills where it looks for them: .agents/skills for Codex, Gemini CLI, Copilot, Cursor, and OpenCode, and .claude/skills for Claude Code.

The um CLI is put on PATH by the Claude Code plugin and by a clone opened in Claude Code. With another agent in a clone, add it with export PATH="$PWD/bin:$PATH". Other agents' plugin installs do not put it on PATH, so install it once:

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

For generated assets, get a fal API key and store it with um fal key set, rather than exporting it from a shell profile or a .env file, per the README. FAL_KEY in the environment still works and wins over the stored key. With no key, fal's OAuth endpoint signs the reader in through the browser, and um comfy makes images on a local ComfyUI server instead.

Recon before building

Start with the two read-only commands. um scan --list lists Steam, Epic, and Xbox installs on the machine. um scan "<game>" takes a fuzzy name or a folder path and prints a report: host, engine with a confidence figure and the evidence behind it, anti-cheat found, loaders installed, save folders, and ranked modding routes with the engine reference file to read next. The scan help text states everything in the scan is read-only. Then search the knowledge base before writing anything:

um kb search "grand theft auto"

A field note for the same game and engine is prior art: the versions that worked, the route, and the gotchas. The game-recon skill then produces a modding plan covering engine and version, managed or native code, anti-cheat, loaders already present, save and config folders, and the community's modding route — and whether the machine at hand can run the game at all, including a Windows game on macOS or Linux. Back up saves with um backup before touching them. The mod-any-game loop's lab step exists because a mod under development can corrupt a save; the backup comes before the first edit, not after the first loss.

What the run found

A run of version 0.2.0, commit 9811709d950979f1b5012dddf10b7ec122d7e95e from October 29, 2026, on Ubuntu 24.04.5 LTS with Python 3.12.3 and no uv installed, used the clone route: the repository was cloned, and um was run from the clone with Python directly. um --help listed all fifteen command groups. um kb search "minecraft" returned six field notes, including a Half-Life weapons pack rebuilt as a Minecraft Fabric mod and a Bloons TD 6 game reproduced inside Minecraft, each marked with its game, engine, route, and status. um scan --list reported no Steam, Epic, or Xbox installs found on that machine. um scan on an empty folder reported an unknown native engine at 10% confidence, no anti-cheat found, no loaders installed, one ranked route, and a warning that the folder was nearly empty and the game was not fully installed or lived elsewhere.

No game was installed on that machine, so no mod was built and nothing was tested in a running game. The run covers the install route, the scan, and the knowledge-base search only. It says nothing about mod quality, about any specific game's engine detection on a real install, or about generated assets: no fal key was set and no asset command ran. A reader with a game installed should expect the scan to report a real engine and real routes, and should still read the field note for that game before building.

Trust score: 5/10

A score is a signal, not a certification. This score rates the toolkit itself, from a run of version 0.2.0 (scan and knowledge-base search, above) and a read of the author's README, agent instructions, safety rules, and skill files. No full code read was done. It does not rate any mod built with the toolkit, and it does not certify that any game may be modded.

The toolkit loses points for the surface its job requires. Its instructions cover debuggers, memory readers, decompilers, and DLL-loader routes, and its skill files carry no tool restrictions in their frontmatter — name and description only — so the agent's scope comes from the body text, not from a declared limit. Its knowledge base is community-written notes that agents read as instructions, and one skill fetches web and forum content, so untrusted text reaches the agent through both paths. Generated assets need a paid fal key, and two sprite services are separate paid services. It keeps points for what the run showed: the scan is read-only by its own help text, the knowledge-base search reads local notes, the only hook in the clone adds the toolkit's bin folder to PATH and does nothing else, and the publish lint exists to catch game files, decompiled dumps, and secrets before sharing. Rescore after any version change that alters the skill set, the hook, or the safety rules, and after a run against a real installed game.

Related skills

Sources

Sources: github.com/rehan-remade/universal-modder, Universal Modder agent instructions, fal.ai.

Related playbooks: Vet a skill before you install it · NVIDIA SkillSpector — scan a skill before you install it

Back to: Skills index