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 UnboundCompute/security-agent-skills --skill hunting-mobile-secret-and-storage-exposuregit clone --depth 1 https://github.com/UnboundCompute/security-agent-skillsWrote 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/unboundcompute/security-agent-skills/hunting-mobile-secret-and-storage-exposure)<a href="https://agentmods.dev/skills/unboundcompute/security-agent-skills/hunting-mobile-secret-and-storage-exposure"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/hunting-mobile-secret-and-storage-exposure/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/unboundcompute/security-agent-skills/hunting-mobile-secret-and-storage-exposure"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/hunting-mobile-secret-and-storage-exposure.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00173 | $0.01943 |
| Opus 5.5 | $0.00069 | $0.00777 |
| Sonnet 5.5 | $0.00035 | $0.00389 |
| Haiku 4.5 | $0.00017 | $0.00194 |
Grade C, and why
hunting-mobile-secret-and-storage-exposure scanned grade C 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 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
Audit only apps you own or are authorized to assess, and extract secrets only from a package or device in How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hunting mobile secret and storage exposure: a real credential a real reader can reach
Not every string that looks like a key is a secret, and not every file an app writes is exposed, so this hunt turns on two questions the noisy scanners skip: is this value actually a credential, and can a party who should not read it actually reach it. A public app identifier shipped in the binary is meant to be public; a value inside the platform sandbox is readable only by the app itself on a non-compromised device. The bug is a live credential in the package or in storage that a reachable party (another app, a device-level reader, a backup, a log sink) can read. You hunt it by finding the mobile-specific sinks and adjudicating both the value's sensitivity and the reader's reach. Stay on mobile-specific storage and packaging; server-side secret handling is a different skill.
When to use
- You have a mobile app package, its embedded resources, and the code that writes storage and logs.
- You see an embedded key or token, a file written to storage, a cache, a log line, or a backup rule.
- You want to know which values are real credentials and which of those a party can actually read.
Scope check
Audit only apps you own or are authorized to assess, and extract secrets only from a package or device in scope, a real embedded credential is a live secret. Treat any credential you surface as sensitive and do not use it. If you can't name the authorization, stop.
The loop
-
Separate credential from public identifier first. For each candidate value, decide whether it is a real secret (a private key, an API secret, a token, a password) or a value meant to be public (a public app or client identifier, a public key, a non-secret configuration constant). Many embedded strings are public by design; only a real credential is a finding, so classify before chasing reach.
-
Check the package for embedded secrets. Look through the app binary, its resources, and its configuration for a live credential compiled or bundled in. Anything shipped in the package is readable by anyone who has the app, so an embedded credential is exposed to every installer by definition.
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 · 128 lines · 173 tokens per session scan C 0f0e59ad209b
hunting-mobile-secret-and-storage-exposure is a skill published in the GitHub repository UnboundCompute/security-agent-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 173 tokens to every session and 1,943 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
swiftui-expert-skill
Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, macOS-specific APIs, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.
prodcheck-review
Review this codebase against the prodcheck pre-production checklists — security, performance, scale, integrations, post-launch readiness and people. Use when asked to check whether a project is ready to ship, to audit an area before launch, or to work through a specific checklist. Produces evidence with file:line…
swiftui-expert-skill
Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, macOS-specific APIs, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.
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 samples using apktool for decompilation, jadx for Java source recovery, and androguard for permission analysis, manifest inspection, and suspicious API call detection.
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.…