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 skydoves/android-testing-skills --skill injecting-input-and-stategit clone --depth 1 https://github.com/skydoves/android-testing-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/skydoves/android-testing-skills/injecting-input-and-state)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/injecting-input-and-state"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/injecting-input-and-state.svg" alt="Measured on agentmods" 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.00208 | $0.05163 |
| Opus 5 | $0.00104 | $0.02582 |
| Sonnet 5 | $0.00042 | $0.01033 |
| Haiku 4.5 | $0.00021 | $0.00516 |
Grade A, and why
injecting-input-and-state 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Injecting Input and State — Drive the Device From the Shell
This skill covers the on-device shell surface a test/QA engineer drives over adb to simulate user gestures, override the screen configuration, flip system settings, reset app state, and launch Activities. Transport (adb devices, USB/TCP) lives in ../../architecture/understanding-adb-architecture/SKILL.md; capturing artefacts after driving the device lives in ../../capture/capturing-screenshots-and-screenrecord/SKILL.md.
When to use this skill
- The developer needs to script a user journey from CI without writing instrumentation: tap, swipe, type text, press hardware keys.
- A bug repro requires a specific screen size or density (
wm size 411x731,wm density 320) without recreating an emulator AVD. - The test suite is flaky because animations are on; the developer wants the canonical hermetic preamble (
window_animation_scale = 0etc.). - The developer needs to clear app data between runs and is unsure whether
am force-stopis enough (it is not). - A script uses
adb shell svc wifi disableand silently does nothing on API 30+ — the moderncmd wifi set-wifi-enabled disabledis the fix. - The developer needs to launch a deep-link Activity with typed extras (
--ez,--ei,--es).
When NOT to use this skill
- The bytes need to leave the device (screenshots, logs, DB). Use
../../capture/capturing-screenshots-and-screenrecord/SKILL.md,../../observability/extracting-logs-with-logcat/SKILL.md,../../transfer/extracting-test-artifacts/SKILL.md. - Driving the device from inside an instrumentation test, not from the host. Use
../../../instrumentation/scenarios/launching-activities-with-activityscenario/SKILL.mdor UiAutomator. - Installing or uninstalling APKs. Use
../../apps/installing-and-managing-apps/SKILL.md. - Connecting to the device in the first place. Use
../../devices/connecting-to-devices/SKILL.mdor../../devices/connecting-over-wifi/SKILL.md.
Prerequisites
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 · 384 lines · 208 tokens per session scan A 369457aa25f5
injecting-input-and-state is a skill published in the GitHub repository skydoves/android-testing-skills (318 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 208 tokens to every session and 5,163 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-30.
Other skills, from other repositories
android-unit-test
Guide for writing and converting Chromium Android unit tests across host Robolectric (chromejunittests) and on-device (chromepublicunittestapk) suites.
android-test-batching
Guide for auditing and applying batching annotations (@Batch) and AutoReset rules (AutoResetCtaTransitTestRule) to Android javatests in Chromium. Use this skill when optimizing Java instrumentation test runtimes, resolving test state leaks, or migrating tests to batched execution.
java-memory-leaks
How to identify and fix Java memory leaks in Android Chrome using LeakCanary traces.
loadline
Running and analyzing LoadLine 1 and 2 benchmarks on Android using Crossbench. Use when you need to measure page loading performance, evaluate performance-related changes in Chrome, or collect Perfetto traces with realistic Chrome workload.
accessibility-cleanup
Finds common violations of the Android accessibility API in the Clank App Java code and attempts to address them (e.g. hardcoded state change announcements, missing events, focus moving, assertive live regions, etc).
remove-unused-object-overrides
Identify and safely remove unreferenced Java Object overrides (equals, hashCode, toString) in Clank to eliminate dead virtual methods from release DEX bytecode while strictly preserving equals/hashCode symmetry.