Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection of eight reverse engineering skills covers the full chain of mobile and game binary analysis. It dumps DEX files from running Android apps, decrypts iOS Mach-O binaries, generates Frida hook scripts, provides IDAPython references for static and dynamic analysis, recovers data structures and function symbols from stripped binaries, extracts Unity IL2CPP method names, and emulates code fragments with the Unicorn engine. It is aimed at mobile security researchers, malware analysts, game security engineers, and vulnerability researchers who need to unpack, deobfuscate, and understand compiled code across platforms.
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Follow the documented setup, then try a first task.
Install the complete reverse-skills bundle
Installs: Complete Reverse Engineering Skills bundle containing the eight documented reverse-engineering skills; the repository describes compatibility with 40+ AI coding agents but does not name specific agents.
Run this command in a terminal to add the complete repository bundle.
<export_directory>: IDA-NO-MCP export directory, unless IDA Pro MCP is connected
Use the rev-struct skill to reconstruct the data structure used by the function at <func_address>. Use either my connected IDA Pro MCP session or the IDA-NO-MCP export in <export_directory>, which should contain decompile/*.c files. Analyze the target function and its immediate callers and callees, then report the inferred fields, offsets, types, estimated size, confidence, and supporting access examples. Do not modify the IDB or source files.
<platform>: target platform, such as Android, iOS, or native
<process_or_package>: process name, package identifier, or PID
<target_symbol_or_method>: export, native function, Java method, or ObjC method
<module_or_class>: containing native module or runtime class
<arguments_to_capture>: arguments that should be logged
Use the rev-frida skill to draft a modern Frida hook script for <platform> and <process_or_package>. Hook <target_symbol_or_method> in <module_or_class>, logging only <arguments_to_capture> and the return value. Do not run or attach the script. State any assumptions and provide the appropriate documented modern Frida CLI form for spawning or attaching.
<func_address>: address inside the target IDA function
Use the rev-idapython skill to write a small IDAPython snippet that runs inside the IDA GUI and iterates over every instruction in the function at <func_address>, printing each instruction address and its disassembly text. Do not patch memory, modify the IDB, or execute the snippet.
Claude