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-android-component-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/auditing-android-component-exposure)<a href="https://agentmods.dev/skills/unboundcompute/security-agent-skills/auditing-android-component-exposure"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/auditing-android-component-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/auditing-android-component-exposure"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/auditing-android-component-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.00172 | $0.01915 |
| Opus 5 | $0.00086 | $0.00958 |
| Sonnet 5 | $0.00034 | $0.00383 |
| Haiku 4.5 | $0.00017 | $0.00192 |
Grade A, and why
auditing-android-component-exposure 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 9d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auditing Android component exposure: what another app on the device can reach and drive
An Android component is only an attack surface if another app can reach it, so this audit is a resolution of the export state and the permission gate, not a scan of component names. A component is exported when a flag says so or an intent filter makes it so by default, and it is exposed only when no permission of a strong enough protection level gates the caller. The bug is a sensitive component another installed app can invoke, and then trust the caller's intent extras to do something it should not. You audit it by resolving, per component, whether it is reachable across the app boundary and what it does with an attacker's intent. Stay on component reachability and inbound-intent handling; when the exposure is a URL the component hands to a WebView, that is the deep-link skill's seam, cross-referenced below.
When to use
- You are reviewing an Android manifest and the activities, services, receivers, or providers it declares.
- A component sets an export flag or an intent filter, or handles intent extras for a sensitive action.
- You want to know which components another app on the device can actually reach and drive.
Scope check
Audit only apps you own or are authorized to assess, and exercise a component only on a device or emulator in scope, invoking an exported component drives real app state. Adjudicate on the manifest and the handler. If you can't name the authorization, stop.
The loop
-
Resolve the export state and permission gate first. For each component, determine whether it is exported: an explicit export flag, or an intent filter that makes it exported by default on the relevant platform version. Then find the permission that gates it, if any, and its protection level. A component is only an attack surface if it is both exported and either ungated or gated by a weak permission; settle both before flagging.
-
Check activities and services. Look for an exported activity or service with no permission gate that performs a sensitive action, changes state, or returns data on behalf of the caller, reachable by any installed app through an explicit or implicit intent.
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.
- 9d ago First seen · 128 lines · 172 tokens per session scan A dd7f3485e793
auditing-android-component-exposure is a skill published in the GitHub repository UnboundCompute/security-agent-skills (5 stars, last pushed today), licensed MIT. It adds 172 tokens to every session and 1,915 once invoked, about $0.0009 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.…