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 krutikJain/android-agent-skills --skill android-media-files-sharinggit clone --depth 1 https://github.com/krutikJain/android-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/krutikjain/android-agent-skills/android-media-files-sharing)<a href="https://agentmods.dev/skills/krutikjain/android-agent-skills/android-media-files-sharing"><img src="https://agentmods.dev/badge/skills/krutikjain/android-agent-skills/android-media-files-sharing/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/krutikjain/android-agent-skills/android-media-files-sharing"><img src="https://agentmods.dev/badge/skills/krutikjain/android-agent-skills/android-media-files-sharing.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.00025 | $0.00995 |
| Opus 5 | $0.00013 | $0.00498 |
| Sonnet 5 | $0.00005 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
android-media-files-sharing 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 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.
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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android Media Files Sharing
When To Use
- Use this skill when the request is about: android file sharing, photo picker android app, fileprovider setup android.
- Primary outcome: Use modern Android file, media, picker, FileProvider, and share-sheet APIs with minimal permissions.
- Reach for this skill when the core problem is content URIs, share-sheet flows, picker choice, or app-to-app file exchange. Use
android-permissions-activity-resultsonly when the hard part is the runtime permission flow itself. - Handoff skills when the scope expands:
android-permissions-activity-resultsandroid-security-best-practices
Workflow
- Start with the asset movement path: pick existing media, open a document, create/export a file, capture new content, or share app-owned content to another app.
- Choose the narrowest platform surface first: Photo Picker, SAF contracts,
FileProvider, or chooser-based sharing before considering broad storage permissions. - Keep file ownership and URI grants explicit with app-private storage, MIME types, temporary grants, and stable authorities.
- Validate return flows, absent-capability fallbacks, and recipient-app interoperability instead of testing only the happy path.
- Hand off runtime permission complexity or deeper hardening only after the URI and sharing contract is correct.
Guardrails
- Prefer Photo Picker, SAF, and chooser APIs over broad media or storage permissions where possible.
- Share content with
content://URIs and temporary grants, never raw file paths. - Keep exported authorities, MIME types, and cache cleanup explicit.
- Treat recipients outside your app as untrusted; validate what leaves the app and what comes back.
Anti-Patterns
- Requesting broad media or storage access when Photo Picker or SAF is enough.
- Sharing
file://paths or world-readable files instead ofFileProviderURIs. - Assuming every recipient app handles every MIME type or URI permission correctly.
- Mixing permission-flow design with file-sharing contract design until both become unclear.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 74 lines · 25 tokens per session scan A 3adf79d633e2
android-media-files-sharing is a skill published in the GitHub repository krutikJain/android-agent-skills (14 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 995 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
navigate
Call the unintent tool with the following exact parameters.
compose-kotlin-agent-skills
Enterprise Android/Kotlin skill for 2026 — Kotlin 2.x K2 compiler, AGP 9, Navigation 3, edge-to-edge Compose, strict MVI with atomic state.update, banned AI antipatterns. Jetpack Compose, Hilt, Room, KMP, CameraX/ML Kit, performance, testing. Use when writing Kotlin for Android, building Compose UI, MVVM/MVI…
android-kotlin-compose
Jetpack Compose UI engineering for 2026 — edge-to-edge, Material 3, recomposition stability, Modifier ordering, LazyColumn performance, and animations. Use when building composables, fixing jank, theming, adaptive layouts, Canvas drawing, auditing screens, or asking "why does my screen recompose", "Modifier order"…
android-kotlin-architecture
Enforces Clean Architecture, MVVM/MVI, and unidirectional data flow for Android apps. Covers UiState, UiEvent, UiEffect, UseCase boundaries, module structure, and atomic ViewModel state via state.update. Use when structuring features, refactoring ViewModels, splitting modules, or asking "MVVM vs MVI", "where does…
android
Senior-level Android engineering expertise for Jetpack Compose, Material 3, shared element transitions, navigation, performance, security, background work, notifications, adaptive layouts, Coil image loading, WorkManager, FCM, Baseline Profiles, R8 optimization, accessibility, coroutines and Flow, and extraordinary UI…
compose-expert
Compose and Compose Multiplatform expert for UI development across Android, Desktop, iOS, and Web. Use whenever the user mentions Compose APIs (@Composable, remember, LaunchedEffect, NavHost, MaterialTheme, LazyColumn, Modifier, recomposition), Compose Multiplatform (commonMain, expect/actual, Res.…