rev-mobile

Automate Android and iOS app reverse engineering with static and dynamic analysis.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Xerrion/opencode --skill rev-mobile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rev-mobile
Source: https://github.com/Xerrion/opencode/tree/main/skills/rev-mobile
Command: npx skills add https://github.com/Xerrion/opencode --skill rev-mobile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mobile reverse engineering across Android and iOS requires coordinated static and dynamic analysis, toolchains, and artifact generation. This skill provides structured workflows to analyze apps from APKs/IPAs to Frida instrumentation and to produce organized outputs under .rev.

Core Features & Use Cases

  • Static Android analysis: apktool unpacking, jadx decompilation, and androguard inspection of AndroidManifest.xml, network_security_config, dex files, assets, and native libraries.
  • Static iOS analysis: class-dump extraction, IPSW handling, and provisioning/entitlements review with notes for downstream tooling like Ghidra.
  • Dynamic analysis: Frida/objection-based instrumentation to bypass SSL pinning and root/jailbreak checks, plus runtime observation.
  • Output conventions: organized artifacts under .rev/decompiled and .rev/disasm with manifest, entitlements, and debug information for audit or research. Use cases: security researchers assessing app behavior, red-team app engagement, and malware analysis workflows.

Quick Start

Begin by applying the Android static workflow to a sample.apk and then perform Frida-based dynamic analysis to generate the .rev outputs.

Frequently Asked Questions about rev-mobile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate mobile app reverse engineering for Android and iOS?

Mobile app reverse engineering is automated by orchestrating static and dynamic analysis workflows. The process unpacks APKs and IPAs, decompiles code, inspects manifests, and instruments runtime behavior to generate structured artifacts under a .rev directory.

What tools are needed for static analysis of an APK?

Static analysis of an APK requires apktool for unpacking, jadx for decompilation, and androguard for inspection. These tools extract the AndroidManifest.xml, network security configs, dex files, assets, and native libraries for review.

Can I bypass SSL pinning and root detection using Frida?

Yes, SSL pinning and root or jailbreak checks can be bypassed using Frida and objection. These dynamic analysis tools enable runtime instrumentation to intercept network traffic and bypass security restrictions on Android and iOS.

How do I extract class information from an iOS IPA?

To extract class information from an iOS IPA, use class-dump for header extraction and IPSW tooling for handling. Provisioning profiles and entitlements are reviewed to prepare notes for downstream disassembly in tools like Ghidra.

What is the best way to organize decompiled app artifacts?

Decompiled app artifacts are organized systematically under a .rev directory. This structure separates decompiled source code and disassembly outputs, keeping manifests, entitlements, and debug information accessible for audit or research.

Does this mobile reverse engineering workflow support malware analysis?

Yes, the workflow supports malware analysis by providing structured static and dynamic inspection. Security researchers can assess malicious app behavior through decompiled artifacts and runtime observation using Frida instrumentation.