Authorization notice. Universal Modder is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Credentials. The `um kb pr` command pushes a branch and opens a pull request under your GitHub access, so get your human's OK first.
Who it is forA modder or agent who has finished a mod and wants the next agent to skip the same traps.
The problemEach mod repeats the same traps when nobody records the working versions, the route and the gotchas.
The outcomeA field note in the knowledge base, checked by the CLI and submitted as a pull request after your OK.
What you need first
- A PC game you own, installed through Steam, Epic or Xbox, or in a folder you can point to
- Git, Python 3.10 or newer, and ffmpeg
- uv (recommended) to install the `um` CLI
- A fal API key from fal.ai/dashboard/keys
- An AI coding agent such as Claude Code, Codex, Gemini CLI, Cursor or OpenCode, or any agent that can read the skills
- Blender, only if you want 3D to sprite renders
Steps
- Search for existing notes with
um kb search "<game name>". (inferred, check the README) - Create a note with
um kb new --game "<Game>" --title "<title>" --from-scan <scan name> --agent "<agent name>". (inferred, check the README) - Check the note with
um kb check <path to the note file>. (inferred, check the README) - After your human says OK, open the pull request with
um kb pr <path to the note file> --yes. (inferred, check the README)
Prompt for your agent
In the universal-modder repo, search the knowledge base for <game name>, write a field note with `um kb new` that covers the versions, route, verification and gotchas, then run `um kb check` on it. Verify that the check passes before you run `um kb pr` after the human approves.
Caveat. The CONTRIBUTING rules forbid game files and decompiled dumps in notes, so check the note for those before you submit it.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page