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 sunnat629/android-media-pack --skill media3-test-utils-robolectricgit clone --depth 1 https://github.com/sunnat629/android-media-packWrote 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/sunnat629/android-media-pack/media3-test-utils-robolectric)<a href="https://agentmods.dev/skills/sunnat629/android-media-pack/media3-test-utils-robolectric"><img src="https://agentmods.dev/badge/skills/sunnat629/android-media-pack/media3-test-utils-robolectric/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/sunnat629/android-media-pack/media3-test-utils-robolectric"><img src="https://agentmods.dev/badge/skills/sunnat629/android-media-pack/media3-test-utils-robolectric.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.00032 | $0.00440 |
| Opus 5 | $0.00016 | $0.00220 |
| Sonnet 5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
media3-test-utils-robolectric 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.
What it actually says
Trigger
Use for Media3 unit tests, Robolectric tests, fake player state, controller/service tests, or adding media3-test-utils.
Rules
- Pin Media3 to
1.10.1through the version catalog. - Put JVM-only test helpers in
testImplementation; put device/UI helpers inandroidTestImplementation. - Test app media state, ownership, and failure behavior; do not over-test Media3 internals.
- Prefer fake player/controller state for UI models and service boundaries.
- Use Robolectric for Android framework behavior that does not need real codec/network hardware.
- Use instrumented tests for decoder, DRM, renderer, surface, and real playback checks.
- Keep sample media tiny, deterministic, and license-safe.
Example
media3-test-utils = { module = "androidx.media3:media3-test-utils", version.ref = "media3" }
media3-test-utils-robolectric = { module = "androidx.media3:media3-test-utils-robolectric", version.ref = "media3" }
assertThat(viewState.isPlaying).isFalse()
assertThat(viewState.errorMessage).isNull()
Do Not
- Do not rely on remote media URLs in unit tests.
- Do not run real DRM or codec assumptions in plain JVM tests.
- Do not assert private Media3 implementation details.
Related
media3-lifecycle-statemedia3-background-playback-servicemedia3-analytics-telemetry
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 · 56 lines · 32 tokens per session scan A 71db0d88efde
media3-test-utils-robolectric is a skill published in the GitHub repository sunnat629/android-media-pack (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 440 once invoked, about $0.0002 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-30.
Other skills, from other repositories
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running end-to-end UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.
argent-create-flow
Create, record, edit, replay, or repair reusable Argent flow YAML files. Use when the user asks to record or replay a repeatable device path, set up profiling or an A/B comparison, or invoke the authoring engine behind argent-qa-flows. Also use before repeating three or more interactions. For one-off UI checks…
argent-ios-device-interact
Drive a physical iPhone through argent. Use when a physical iPhone is involved (a list-devices iOS entry with kind "device") and ONLY then; never for a simulator. For cable, trust, or signing problems read argent-ios-device-setup.