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 prasad-vennam/Awesome-Android-AI-Agent-Skills --skill android-hardware-testinggit clone --depth 1 https://github.com/prasad-vennam/Awesome-Android-AI-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/prasad-vennam/awesome-android-ai-agent-skills/android-hardware-testing)<a href="https://agentmods.dev/skills/prasad-vennam/awesome-android-ai-agent-skills/android-hardware-testing"><img src="https://agentmods.dev/badge/skills/prasad-vennam/awesome-android-ai-agent-skills/android-hardware-testing/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/prasad-vennam/awesome-android-ai-agent-skills/android-hardware-testing"><img src="https://agentmods.dev/badge/skills/prasad-vennam/awesome-android-ai-agent-skills/android-hardware-testing.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.00016 | $0.00349 |
| Opus 5 | $0.00008 | $0.00175 |
| Sonnet 5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
android-hardware-testing 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 12d 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
Android UIAutomator & System Testing 🤖
Testing that extends beyond a single application boundary into the OS itself.
⚡ When to Use
- When writing tests spanning multiple apps, interacting with system notifications, or performing Home button interactions.
🏗️ Core Rules / Pillars
1. UIAutomator Fundamentals
- Pattern: Espresso / Compose Rule testing CANNOT interact with System Dialogs (like Permission Popups). You MUST use UIAutomator to click system buttons.
- Implementation: Use
UiDevice.getInstance(InstrumentationRegistry.getInstrumentation())to find notification shades, click permission "Allow" buttons, and press the physical hardware back button.
2. Mocking Hardware Sensors
- Pattern: End-to-end tests relying on BLE, GPS, or NFC will randomly flake on CI servers.
- Implementation: Introduce a Fake/Mock layer behind an interface (e.g.,
LocationProvider) to stub out sensor values during test variants instead of simulating complex location spoofing over ADB.
🚧 Critical Anti-Hallucination Guards
- Trap: Never use
Thread.sleep()to wait for a system animation. Always useUiDevice.wait(Until.hasObject(By.text("Welcome")), 5000)to ensure tests don't flake on slow emulators.
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.
- 12d ago First seen · 34 lines · 16 tokens per session scan A a4ce3c090770
android-hardware-testing is a skill published in the GitHub repository prasad-vennam/Awesome-Android-AI-Agent-Skills (9 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 349 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-08-31.
Other skills, from other repositories
jetson-video-pipeline
Use when executing and verifying Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or acceptance workflows with exact artifact handoffs.
mixed-signal-cosim
Run mixed-signal co-simulation — digital gate-level Verilog + analog behavioral models together. Use when the user says "mixed-signal sim", "co-simulation", "digital-analog integration test", or at Step A9 of the analog track.
native-sim
Host-based simulation using the Zephyr nativesim board. Covers building for Linux/macOS/Windows, automated testing, host-side debugging (GDB, Valgrind), and host-target integration. Trigger when developing application logic without hardware or setting up CI/CD tests.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.