agentleFS
Sign inStart free
noahfranklinnoahfranklin/gideon/skills/mobile-pentest/SKILL.md

mobile-pentest

Skill2 starsChanged 47 days agoMITView on GitHub

Use when testing an Android or iOS mobile application for security issues — insecure data storage, weak crypto, insecure communication, authentication, platform misuse, reverse engineering / tampering resistance, and hardcoded secrets. Follows OWASP MASTG/MASVS and covers static, dynamic, and network testing. Authorized engagements only.

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agentic-app-audit, client-reverse and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • shuvonsecSkill

    agentic-app-audit

    Black-box security audit of a DEPLOYED AI agent (not the MCP server behind it) — tool-call hijacking, cross-session memory poisoning, confused-deputy via connected tools, agent-to-agent IDOR, excessive agency / unconfirmed destructive actions, and privilege compromise where the agent holds broader perms than the user. Use when the target is a live assistant/agent product with tool access (bookings, email, payments, file/RAG, browsing) rather than a raw LLM chat box or an MCP server you can read.

    Also in 3 projects that use this

  • shuvonsecSkill

    client-reverse

    Client-side request-signing and anti-bot token reversal for bug bounty — when a request carries a sign/sig/hmac/token/nonce/timestamp/X-Sensor header that Burp Repeater cannot replay, recover the signer just enough to reproduce the request outside the client. Packet-first staging (capture real request → prove replay works → only reverse if replay fails) across the locate→recover→runtime→validation→replay spine. Covers tracing backward from the signature field (writer→builder→entry→source), isolating user-mutable sign inputs (timestamp/nonce/deviceId/body) vs constants (secret key), hooking fetch/XHR in DevTools, JS deobfuscation basics (webpack/wasm/JSVMP), and the bounty payoff: reach the protected API to then hunt IDOR/auth/business-logic. Use when Burp/mitmproxy replay of a signed or anti-bot-gated request fails and you suspect a client-computed field is blocking you.

    Also in 3 projects that use this

  • Mikacr1138Skill

    web2-vuln-classes

    Complete reference for 18 web2 bug classes with root causes, detection patterns, bypass tables, exploit techniques, and real paid examples. Covers IDOR, auth bypass, XSS, SSRF (11 IP bypass techniques), SQLi, business logic, race conditions, OAuth/OIDC, file upload (10 bypass techniques), GraphQL, LLM/AI (ASI01-ASI10 agentic framework), API misconfig, ATO taxonomy, SSTI, subdomain takeover, cloud/infra misconfigs, HTTP smuggling, cache poisoning. Use when hunting a specific vuln class or studying what makes bugs pay.

    Also in 3 projects that use this

  • hhjkjkjkSkill

    meme-coin-audit

    Meme coin and token security audit — rug pull detection (honeypot, hidden mint, fee manipulation, LP lock bypass), Solana SPL token analysis (freeze authority, mint authority, metadata mutability), Token-2022 extension risks (transfer hooks, permanent delegate), DEX liquidity pool attacks (sandwich amplification, LP drain, bonding curve exploits), pump.fun/Raydium/Jupiter integration risks, token_scanner.py automation, and real exploit examples from 2024-2025. Use for any token audit, rug pull assessment, meme coin security review, or pre-investment due diligence.

    Also in 3 projects that use this

  • hhjkjkjkSkill

    bb-methodology

    Use at the START of any bug bounty hunting session, when switching targets, or when feeling lost about what to do next. Master orchestrator that combines the 5-phase non-linear hunting workflow with the critical thinking framework (developer psychology, anomaly detection, What-If experiments). Routes to all other skills based on current hunting phase. Also use when asking "what should I do next" or "where am I in the process.

    Also in 3 projects that use this

  • Mikacr1138Skill

    security-arsenal

    Security payloads, bypass tables, wordlists, gf pattern names, always-rejected bug list, and conditionally-valid-with-chain table. Use when you need specific payloads for XSS/SSRF/SQLi/XXE/IDOR/path-traversal, bypass techniques, or to check if a finding is submittable. Also use when asked about what NOT to submit.

    Also in 3 projects that use this

  • +4 more from shuvonsec

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Fix: never rely on client-side secrets or client-side security decisions.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Mobile Application Penetration Testing

Assessment of Android/iOS apps following the OWASP Mobile Application Security Testing Guide (MASTG) and verified against the MASVS controls. Combines static (the package), dynamic (running app), and network testing.

0. Authorization gate

  • Written authorization for the app + its backend/APIs.
  • Test devices/accounts provided; jailbreak/root allowed?
  • Backend testing scope (usually pair with api-security-audit).

1. Setup

  • Obtain the build (APK/AAB, IPA). Prepare instrumented device/emulator.
  • Intercept TLS via a proxy; handle certificate pinning (bypass only on your test build/device, in scope).

2. MASVS areas — test & fix

Storage (MASVS-STORAGE)

  • Inspect local storage: shared prefs, SQLite, keystore/keychain usage, cached files, logs, backups.
  • Look for: PII/tokens/secrets stored in cleartext or world-readable locations.
  • Fix: platform keystore/keychain, no sensitive data in logs/backups.

Crypto (MASVS-CRYPTO)

  • Hardcoded keys, weak algorithms, custom crypto, static IVs.
  • Fix: platform crypto APIs, keys in hardware-backed keystore.

Auth & session (MASVS-AUTH)

  • Local auth bypass, insecure biometric gating, token handling, session invalidation.
  • Fix: enforce auth server-side; biometrics gate local secrets, not trust.

Network (MASVS-NETWORK)

  • TLS validation, certificate pinning presence/quality, cleartext traffic.
  • Fix: TLS everywhere, pin certs, disable cleartext.

Platform interaction (MASVS-PLATFORM)

  • Exported components (activities/services/receivers/providers), deep links, IPC, WebView misconfig (JS bridges, file access), clipboard/screenshot leakage.
  • Fix: minimize exported surface, validate intents/deep links, harden WebViews.

Code quality & resilience (MASVS-CODE / MASVS-RESILIENCE)

  • Reverse engineering: decompile to review logic, find secrets/endpoints.
  • Anti-tampering / root-jailbreak detection / obfuscation quality (resilience is defense-in-depth, not a primary control).
  • Fix: never rely on client-side secrets or client-side security decisions.

3. Static + dynamic + backend

  • Static: decompile, scan manifest/Info.plist, search for secrets/URLs, review permissions.
  • Dynamic: runtime instrumentation to observe storage, crypto calls, and bypass client-side checks (in-scope build).
  • Backend: the app's APIs almost always carry the real risk → run api-security-audit.

4. Tooling

apktool/jadx (Android), Hopper/Ghidra, Frida/Objection (dynamic instrumentation), MobSF (automated triage), proxy (Burp/ZAP), platform SDK tools.

5. Reporting

Per finding: MASVS control, platform, component, severity, reproduction, remediation. Emphasize that client-side controls are bypassable — real fixes live server-side. Checklist: references/mobile-checklist.md.

<sub>© 2026 noahfranklin · Part of the Gideon security suite · MIT License · Original work.</sub>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free