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 auditing-mobile-deeplink-trustgit 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/auditing-mobile-deeplink-trust)<a href="https://agentmods.dev/skills/unboundcompute/security-agent-skills/auditing-mobile-deeplink-trust"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/auditing-mobile-deeplink-trust/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/auditing-mobile-deeplink-trust"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/auditing-mobile-deeplink-trust.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.00192 | $0.02009 |
| Opus 5 | $0.00096 | $0.01005 |
| Sonnet 5 | $0.00038 | $0.00402 |
| Haiku 4.5 | $0.00019 | $0.00201 |
Grade A, and why
auditing-mobile-deeplink-trust 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 11d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auditing mobile deep-link trust: when an attacker's URL drives a trusted action
A deep link is attacker-reachable input: a custom scheme any app can claim, or a link another app or a web page can fire, carrying parameters the app routes into an action. The bug is trusting that URL, letting a parameter reach a sensitive operation, or handing an attacker-controlled URL to a WebView that exposes a JavaScript bridge back into the app. This audit reads the deep-link routing, the URL handling, and the WebView configuration and asks, per link, whether an attacker-supplied URL can drive something it should not. It pairs with the component-exposure skill: that one owns whether the receiving component is reachable across the app boundary, this one owns whether the URL it carries is trusted. Keep the seam clean so a single flaw is reported once.
When to use
- The app registers a custom scheme, an app link, or a universal link, and routes the URL to an action.
- A deep-link parameter flows into navigation, a WebView load, an authentication step, or a state change.
- You want to know whether an attacker-supplied URL can drive a sensitive action or reach a trusted WebView.
Scope check
Audit only apps you own or are authorized to assess, and fire a deep link only at a device or emulator in scope, a crafted link drives real app state and can complete real actions. Adjudicate on the routing and the WebView config. If you can't name the authorization, stop.
The loop
-
Establish which links are attacker-controllable first. Determine how each link is registered: a custom scheme (any app can also register it and intercept or forge it), an app or universal link with a verified domain association (only the app resolves it), or one whose association is unverified (not exclusive). The registration decides whether an attacker can send or hijack the link; settle it before judging the handler.
-
Check scheme hijack and association. Look for a custom scheme carrying sensitive data or actions, which a malicious app can register to intercept or forge, and for an app link whose domain association is missing or unverified, so the link is not exclusively the app's and can be claimed or spoofed.
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.
- 11d ago First seen · 129 lines · 192 tokens per session scan A a64c8b8abda5
auditing-mobile-deeplink-trust is a skill published in the GitHub repository UnboundCompute/security-agent-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 192 tokens to every session and 2,009 once invoked, about $0.0010 per session on Opus 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-31.
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 and post-launch readiness. 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 citations…
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.…