More screenshots
Works with the AI Agents you already use
Mobile Reverse: Analyze Android and iOS Apps with Evidence
Reverse-engineer Android and iOS apps for authorized assessment — start from the question, pick the lightest tool, produce reproducible evidence.
$5
Mobile Reverse: Analyze Android and iOS Apps with Evidence
Example session with this skill installed
A client wants to know where their Android app's auth token comes from and whether it is stored safely. Answer with evidence.
- Read your context and instructions
- Compiled the mobile reverse
Question first: 'where does the auth token come from, and where is it stored?' — not 'reverse the app'. That question picks the tools: static analysis of the auth flow, then a Frida hook on the token storage call, then network capture. Unpacking: the APK was extracted and the dex reviewed; the app is not heavily obfuscated, so no deobfuscation detour — the lightest sufficient tool rule saved a day. The auth flow reads clearly: login returns a token, which is written to encrypted shared preferences. Network before binary: captured the login traffic first and confirmed the token arrives over TLS with certificate pinning in place — pinning verified by the fact that a proxy without the bypass failed, and the Frida bypass was used only in the lab, on the client's own app, with authorization. Dynamic: hooked the token-write call with Frida and watched the exact value written, the key name, and the encryption call that wraps it. The token is encrypted at rest with a key from the Android Keystore — the storage is sound. The finding is elsewhere: the token is also logged in plaintext by a debug logging call left in the release build. The log line includes the full token, readable by any app with log access on older Android versions. Severity medium, fix one line. Evidence: every claim carries its source — the dex method name, the Frida hook output, the captured request, and the log line. The report answers the original question directly: the token comes from the login endpoint, it is stored encrypted via the Keystore, and the exposure is the debug log, not the storage.
Connects securely to your tools. The creator never sees your data.
About this skill
Most mobile RE guides hand you a phase list and a tool table. This one starts from the question you are actually trying to answer, because the question determines the tools — and the lightest sufficient tool is always the right one. It covers the Android unpacking ladder, the iOS specifics that actually differ, dynamic analysis with Frida and Objection driven by intent rather than curiosity, network analysis before binary analysis, and an evidence discipline that makes the work reproducible. All work assumes explicit authorization: your app, a client engagement, or a bug-bounty scope. If you cannot name the authorization, stop.
Authorized assessment only: your app, a client engagement, or a scoped bounty. It is not a tool for cracking apps, bypassing licenses, or stealing data.
Heavily obfuscated apps may need a deobfuscation detour the skill does not cover in depth.
iOS and Android differ in real ways; the skill flags the differences rather than pretending one workflow fits both.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 days ago
Permissions
No special permissions declared or detected