Reverse Engineering

Prerequisites: Python with uv or pipx (for the optional um toolkit CLI); reverse-engineering tools installed as needed (ILSpy, Ghidra, Frida, Cheat Engine, RenderDoc, depending on the game). Install "Reverse Engineering" for me. It reads how a game actually works so a mod can hook into it: decompiling .NET/IL2CPP/Java/native code, data formats, live memory analysis and render-pass inspection. Repository: https://github.com/rehan-remade/universal-modder 1. Fetch the SKILL.md file (and any helper files) from the repository path skills/reverse-engineering/ into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "reverse-engineering". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install a decompiler). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me. Single-player or offline games only; never attach tools to a game with anti-cheat.