Game Recon
Figure out how a specific installed game can be modded, before writing any mod code.
Install
npx skills add rehan-remade/universal-modder --skill game-recon -g -a claude-code -y- Repository
- rehan-remade/universal-modder9.3k
- Category
- Writing
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 1,095 tokens
- Runs scripts
- No, instructions only
What it does
Figure out how a specific installed game can be modded, before writing any mod code. Covers where it's installed, the engine and version, managed vs native code, anti-cheat, loaders already present, save and config folders, and the community's modding route. Also whether this machine can run it (a Windows game on macOS or Linux, x64 on ARM). Use when the user asks "can I mod <game>?", "what engine is <game>", "how do people mod <game>", or at the start of any modding task. Produces MODDING_PLAN.md.
Game recon
Goal: in about five minutes, know what you're dealing with and which route to take. Write the answer down so every later step can rely on it.
0. Has another agent been here?
um kb search "<game>" (and the engine name). A field note in the shared knowledge base can hand you the
working versions, the route, and the gotchas before you touch anything. See the share-field-notes skill.
1. Find it and fingerprint it
um scan --list # Steam, Epic and Xbox installs (Windows, WSL, Linux, macOS)
um scan "<name or folder>" # host, engine, version, exes (.NET?), anti-cheat, loaders,
# mod folders, saves, routes
um scan "<game>" --json # the same, machine-readable
um lives at bin/um in the universal-modder repo (plugins and clones put it on PATH). Anywhere else:
uv tool install git+https://github.com/rehan-remade/universal-modder.
um scan reads files only. It indexes the install (bounded), sniffs PE headers, the Unity/Godot/GameMaker
headers and the Unreal version string, maps known games to their community loader, and points to the
playbook to read: skills/mod-any-game/references/engines/<engine>.md.
The scan can't see everything, so check these by hand:
- Game not in a store library (GOG, itch, a standalone folder): pass the folder path.
- Several engines' signals: launchers and web helpers are common. The top score wins, but read the "also" line.
- Anti-cheat installed elsewhere: kernel drivers (Vanguard's
vgk.sys) and launcher-level protection don't live in the game folder. Search "<game> anti-cheat". - Online-only or live-service games: treat them as protected even if nothing was detected.
