mobile-pentest

Mobile app pentest for bug bounty (Android APK + iOS IPA) — runtime-first workflow: install app, proxy through Burp/mitmproxy, drive the UI, capture packets, then test the API exactly like a web target; escalate to decompile (apktool/jadx) and Frida/objection only when traffic is SSL-pinned, encrypted, or absent. Covers APK/IPA decompile for hardcoded secrets + hidden API endpoints + base URLs the web app never exposes, exported-activity and deeplink intent injection, WebView addJavascriptInterface bridge abuse, SSL pinning bypass (objection patchapk / Frida CertificatePinner + checkServerTrusted hooks), OkHttp interceptor chain to recover request signing, JNI native-lib triage, and the quick apktool/grep secret + endpoint sweep. Use when the program scope includes a mobile app, when web recon dries up and you need a fresh attack surface, or when traffic is pinned and you must MitM it.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable, executable mobile pentest guidance with a clear runtime-first workflow and explicit validation/escalation checkpoints. The main weakness is progressive disclosure: it is a long single-file skill with no reference bundle, so a chunk of the Frida scripts and sweep recipes that could be offloaded to reference files instead sit inline.

Suggestions

Move the reusable Frida scripts (pin-bypass.js, the signer dump hook, the universal-unpinning codeshare invocation) into a ./references/ or ./scripts/ file and link to it from the relevant sections, keeping only a short snippet inline.

Extract the static-sweep grep recipes and the 'Found in APK → Action' table into a ./references/static-sweep.md so the SKILL.md body stays a navigable overview.

Trim the framing prose (the opening 'Most hunters skip mobile. That's the edge.' paragraph and the 'REAL PAID EXAMPLES' section) to tighten token efficiency while preserving the impact-first guidance.

Dimension	Reasoning	Score
Conciseness	Largely lean and code-dense with every block earning its place, but the prose framing (the opening 'the edge' paragraph, 'REAL PAID EXAMPLES', and a few rhetorical callouts) pads slightly beyond what Claude strictly needs.	4 / 5
Actionability	Fully executable guidance throughout — copy-paste bash (apktool/jadx/adb/objection commands), complete Frida JS hooks (pin-bypass.js, signer dump), and concrete adb deeplink probes with real flag values covering the common cases.	5 / 5
Workflow Clarity	Clear runtime-first sequence with explicit validation checkpoints ('After each action, check the proxy: are requests visible and replayable?', 'Traffic visible + replayable → STOP', 'Traffic pinned / encrypted / absent → THEN escalate') and feedback loops for error recovery (objection fails → targeted Frida hook).	5 / 5
Progressive Disclosure	Well-organized with clear section headers and a coherent in-file structure, but it is a monolithic ~324-line SKILL.md with no bundle files and no one-level-deep external references — the Frida scripts, secret-sweep commands, and impact-ladder tables are content that could live in separate reference files.	3 / 5
	Total	17 / 20 Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that names concrete actions, comprehensive trigger terms, and explicit what/when guidance in third-person voice. It is long but every clause earns its place; the only minor gap is slight conceptual adjacency to general web-pentest skills, though the mobile framing and trigger clauses mitigate that.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'install app, proxy through Burp/mitmproxy, drive the UI, capture packets', 'APK/IPA decompile for hardcoded secrets', 'SSL pinning bypass (objection patchapk / Frida CertificatePinner + checkServerTrusted hooks)', 'OkHttp interceptor chain to recover request signing' — with comprehensive coverage of the mobile pentest workflow.	5 / 5
Completeness	Explicitly answers both what ('runtime-first workflow: install app, proxy... test the API exactly like a web target; escalate to decompile...') and when ('Use when the program scope includes a mobile app, when web recon dries up and you need a fresh attack surface, or when traffic is pinned and you must MitM it').	5 / 5
Trigger Term Quality	Comprehensive natural terms including synonyms and file extensions: 'Android APK + iOS IPA', 'SSL-pinned', 'decompile', 'Frida/objection', 'when web recon dries up', 'when traffic is pinned and you must MitM it', covering both user-natural and technical phrasing.	5 / 5
Distinctiveness Conflict Risk	Clear niche (mobile app pentest for bug bounty, APK/IPA specifically) with distinct runtime-first framing; minor overlap risk with general web pentest skills given it explicitly hands off to web2-vuln-classes, but the mobile-specific triggers keep it distinguishable.	4 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: shuvonsec/claude-bug-bounty
Path: skills/mobile-pentest/SKILL.md
Commit: 0826b13

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.