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 trilwu/secskills --skill bypassing-mobile-pinninggit clone --depth 1 https://github.com/trilwu/secskillsWrote 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/trilwu/secskills/bypassing-mobile-pinning)<a href="https://agentmods.dev/skills/trilwu/secskills/bypassing-mobile-pinning"><img src="https://agentmods.dev/badge/skills/trilwu/secskills/bypassing-mobile-pinning/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/trilwu/secskills/bypassing-mobile-pinning"><img src="https://agentmods.dev/badge/skills/trilwu/secskills/bypassing-mobile-pinning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Privilege Escalation · line 68 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00099 | $0.02587 |
| Opus 5 | $0.00049 | $0.01293 |
| Sonnet 5 | $0.00020 | $0.00517 |
| Haiku 4.5 | $0.00010 | $0.00259 |
Grade A, and why
bypassing-mobile-pinning 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 7d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
adb shell chmod 644 /system/etc/security/cacerts/9a5ba580.0 Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bypassing Mobile Pinning
Most time lost here is spent bypassing pinning that was never there. An empty proxy has at least six causes, and the fix for each is different — one of them is not pinning at all but Android's default distrust of user CAs, and another is that the app has its own TLS stack and never saw your proxy. Diagnose before you reach for a bypass script.
Use only against apps you are authorized to test.
When to Use
- Burp/mitmproxy/Charles shows a TLS handshake failure from a mobile app
- The proxy shows nothing while the app clearly reaches the network
- The app reports "network error", "connection insecure", or similar with the proxy configured
- You know the target pins, and need the right hook for its stack
When NOT to Use
- Flutter targets — use
reversing-flutter-apps; Flutter's failure looks identical but the cause and fix are specific to its engine - The wider mobile assessment — use
testing-mobile-applications - The backend once traffic is visible — use
testing-apis - Reversing a native
.soin depth — useanalyzing-binaries
Diagnose First
Run this before installing anything. The symptom tells you the cause.
| Symptom | Likely cause | Fix |
|---|---|---|
Proxy sees the CONNECT, then TLS alert unknown_ca / bad_certificate |
Your CA is not trusted | Install as system CA, or patch Network Security Config |
| Proxy sees the CONNECT, then alert only for some domains | Real pinning, scoped to those hosts | Hook the pinning check |
| Proxy sees nothing at all, app works | App ignores the system proxy | Force traffic at the network layer (Flutter, gRPC, some SDKs) |
| Proxy sees the handshake, server rejects the client | Mutual TLS — the app presents a client certificate | Extract the client cert; this is not pinning |
| Works on emulator, fails on device (or vice versa) | Root/emulator detection, not TLS | Different problem — see the detection section |
| Fails only after login | Pinning applied to the API host only | Hook, then re-check |
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.
- 7d ago First seen · 214 lines · 99 tokens per session scan A 808fcf7a94cc
bypassing-mobile-pinning is a skill published in the GitHub repository trilwu/secskills (138 stars, last pushed 7d ago), licensed MIT. It adds 99 tokens to every session and 2,587 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
google-mobile-ads-android-migrate-to-next-gen
Migrates Android applications from the old, legacy Google Mobile Ads (GMA) SDK (com.google.android.gms:play-services-ads) to the new GMA Next-Gen SDK (com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk). Provides comprehensive mapping tables for imports, classes, and method signatures to help determine…
developer-device-platform-basics
Provides guidance and instructions on managing remote devices on Developer Device Platform (DDP). Use when reserving remote Android devices, establishing connection tunnels, checking session status, or extending/cancelling leases. Don't use for iOS or local device/hardware inquiries.
google-mobile-ads-validate
Validates a project's Google Mobile Ads (GMA) SDK integration for iOS, Android, or Unity projects. Use when conducting a full pre-launch audit of an app that integrates GMA SDK or when validating any individual GMA SDK integration checks, such as when validating ad unit IDs and ad formats, SKAdNetwork IDs, mediation…
google-mobile-ads-interstitial
Provides instructions for implementing, integrating, or configuring Google Mobile Ads (GMA) SDK interstitial ads in Android, iOS, or Unity mobile applications. Use when the task involves setting up interstitial ads. Don't use for "rewarded interstitial" ads.
google-mobile-ads-rewarded
Provides instructions for implementing, integrating, or configuring Google Mobile Ads (GMA) SDK rewarded ads in Android, iOS, or Unity mobile applications. Use when the task involves setting up rewarded ads. Don't use for "rewarded interstitial" ads.
leanback-to-compose-tv-migration
Provides instructions and architectural patterns for migrating Android TV applications from legacy Leanback UI Toolkit, Android Views, or Support Fragments to Jetpack Compose for TV (androidx.tv). Use this skill for Leanback to Compose migrations, including browse screen, settings screen, authentication screen, login…