Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add transilienceai/communitytools --skill mobile-securitygit clone --depth 1 https://github.com/transilienceai/communitytoolsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/transilienceai/communitytools/mobile-security)<a href="https://agentmods.dev/skills/transilienceai/communitytools/mobile-security"><img src="https://agentmods.dev/badge/skills/transilienceai/communitytools/mobile-security/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/transilienceai/communitytools/mobile-security"><img src="https://agentmods.dev/badge/skills/transilienceai/communitytools/mobile-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 61 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 13 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00090 | $0.02446 |
| Opus 5.5 | $0.00036 | $0.00978 |
| Sonnet 5.5 | $0.00018 | $0.00489 |
| Haiku 4.5 | $0.00009 | $0.00245 |
Grade A, and why
mobile-security scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Security
Scope
End-to-end mobile application VAPT for Android (APK/AAB) and iOS (IPA), aligned to the OWASP MASVS v2.x control groups and the MASTG testing process. Four complementary tiers:
- Static reverse engineering of compiled artifacts — Dart AOT snapshots, Unity IL2CPP, React Native/Hermes bytecode, native ARM64
.so/Mach-O, smali. Recover secrets, endpoints, and the crypto contract without a device. - SAST — manifest /
Info.plist, exported-component & IPC surface, WebView, local storage, cryptographic-primitive weakness, code-signing, and automated baseline (MobSF/apkid/apkleaks) → then manual deep-dive. - Dynamic analysis (DAST) — Frida/objection instrumentation, traffic interception, TLS-pinning bypass across stacks, Keychain/Keystore runtime dumps, IPC probing, and root/jailbreak/anti-tamper defeat for MAS-L2 / MASA scope.
- Privacy — data-collection inventory, tracker/SDK enumeration, PII leakage, declared-vs-actual (Play Data Safety / Apple Privacy Manifest).
Static dump first (faster, no device); dynamic is a first-class phase whenever a control can only be proven at runtime (enforced pinning, Keystore-backed keys, root reaction, IPC guards). Cross-asset stitching, scoring, and reporting are owned by sibling skills — this skill produces MASVS/MASTG-tagged findings and hands them off.
Coverage contract
In a coverage-mode engagement (pentest-engagement mobile mode) completion is code-enforced, not narrative. Two surfaces are gated, and both are mandatory:
| Surface | File | Classes |
|---|---|---|
| The app bundle | recon/inventory/mobile-surface.json |
the 15 MAS-* MASVS classes |
| The backend recovered from the bundle | <apex>-api/recon/inventory/surface.json |
the ordinary OWASP API/web classes |
The second row is where the material risk has historically been. A decompiled bundle hands you the full server contract, and that surface is not browser-reachable — so it is systematically under-tested by everyone, including the app's own developers. Recovering the endpoint inventory and driving it through the API classes is not an optional extra; a bundle that yields zero endpoints is treated as a failed acquisition.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- reference/android-dynamic-analysis.md 12 KB
- reference/android-static-analysis.md 11 KB
- reference/flutter-aot-reversing.md 4.9 KB
- reference/ios-dynamic-analysis.md 12 KB
- reference/ios-static-analysis.md 13 KB
- reference/masvs-class-map.md 9.3 KB
- reference/methodology.md 12 KB
- reference/privacy-testing.md 11 KB
- reference/scenarios/android/native-lib-host-extraction.md 6.3 KB
- reference/scenarios/android/react-native-hermes.md 8.1 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 85 lines · 90 tokens per session scan A 82a29a5f6a66
mobile-security is a skill published in the GitHub repository transilienceai/communitytools (591 stars, last pushed 2mo ago), licensed MIT. It adds 90 tokens to every session and 2,446 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.…
ios-exploiting
A research guide for examining iOS operating-system components, including kernel files, with virtual devices, jailbroken phones, emulators, and binary comparison tools. Corellium is a cloud service that can run virtual iOS devices.
ios-pentesting
A guide to choosing devices and tools for testing iPhone and iPad apps. It compares jailbroken and non-jailbroken devices, injected testing tools, and the Xcode Simulator, which runs iOS apps on a Mac.
wechat-miniprogram-pentesting
A security-testing guide for WeChat Mini Programs, which are lightweight apps that run inside WeChat.
mobile-backend
A guide to security testing for the APIs used by mobile apps to communicate with their servers.
android-app-pentesting
A guide to testing Android apps from their install packages and while they run. It covers code and manifest inspection, runtime instrumentation, network traffic, stored data, app components, WebViews, and device-protection checks.