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 agentmods add skills/evilfreelancer/secs/testing-mobile-applicationsnpx skills add EvilFreelancer/secs --skill testing-mobile-applicationsgit clone --depth 1 https://github.com/EvilFreelancer/secsWrote 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/evilfreelancer/secs/testing-mobile-applications)<a href="https://agentmods.dev/skills/evilfreelancer/secs/testing-mobile-applications"><img src="https://agentmods.dev/badge/skills/evilfreelancer/secs/testing-mobile-applications.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00109 | $0.02405 |
| Opus 5 | $0.00055 | $0.01203 |
| Sonnet 5 | $0.00022 | $0.00481 |
| Haiku 4.5 | $0.00011 | $0.00241 |
Grade A, and why
testing-mobile-applications scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL "https://defuddle.md/<url>" # scheme in the path is optional How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Mobile Applications
A mobile app ships to the attacker's device. Anything it stores, hardcodes, or trusts client-side is readable by a motivated user with a rooted phone and Frida. So the assessment is not "can the UI be fooled" but "what does the client hold that the server should have owned" — session tokens in plaintext preferences, API keys in the binary, authorization decided on the handset, pinning that a one-line hook removes. Test the client to find the server's mistakes.
Scope and authorization gate first: confirm the package IDs (and backend API hosts, if in scope) are on the allow-list before touching anything, per AGENTS.md. The app's backend is a separate asset — testing it needs its own authorization, and third-party SDKs and analytics endpoints the app talks to are out of scope unless explicitly named.
When to Use
- Black-box or gray-box assessment of an Android or iOS application
- Auditing on-device storage (SharedPreferences, Keychain, SQLite, files) for secrets or PII
- Bypassing TLS certificate pinning to inspect the app's API traffic
- Testing authentication, session handling, and biometric/local-auth gates
- Reviewing exported components, deep links, and custom URL schemes for abuse
- Assessing root/jailbreak detection, tamper resistance, and other resilience controls
When NOT to Use
- The backend API itself — use
testing-apis; the mobile client is the lens, but auth/IDOR/mass-assignment flaws in the API are that skill's job - A WebView-heavy or hybrid app's web layer — use
testing-web-applicationsfor the DOM/JS/XSS surface - Reverse-engineering a native library or recovering an algorithm — use
analyzing-binariesfor the.so/Mach-O internals - A suspected-malicious APK/IPA — use
analyzing-malware; detonate for behavior, do not "pentest" it - Imaging a seized handset for evidence — that is device forensics under
responding-to-incidents, not app testing - Writing up what you found — use
reporting-security-findings
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.
- 3d ago First seen · 190 lines · 109 tokens per session scan A 10a3f9ca6358
testing-mobile-applications is a skill published in the GitHub repository EvilFreelancer/secs (10 stars, last pushed 25d ago), licensed Apache-2.0. It adds 109 tokens to every session and 2,405 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
analyzing-ios-app-security-with-objection
Runtime iOS app security testing with Objection (Frida): inspect keychain and filesystem data, explore app internals at runtime, and validate/bypass client-side protections during authorized mobile assessments.
analyzing-android-malware-with-apktool
Perform static analysis of Android APK malware using apktool for resource decompilation, jadx for Java source recovery, and androguard for manifest inspection, dangerous permission-combination detection, and identification of obfuscated code, dynamic code loading, and reflection-based API calls. Use to statically…
redteam-mobile-detail-pack
Domain routing and boundary guidance for authorized mobile application security testing, including insecure storage, certificate pinning bypass, exposed components, and binary reverse engineering. Use when a task belongs to the mobile testing domain and needs scope, evidence, pivot, or exit criteria.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
Blue Team Defense & Hardening
System hardening, detection engineering, security baseline monitoring, patch management, defense-in-depth architecture, and security posture improvement.
designing-hardware-products
AI-automated hardware product pipeline: from requirements to manufacturable Gerber + compiled firmware + cross-platform app. Orchestrates system design, ESP-IDF firmware, KiCad PCB, UniApp client, and release packaging in a zero-human-touch flow.