Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/skydoves/android-testing-skillsnpx agentmods add skills/skydoves/android-testing-skills/capturing-screenshots-and-screenrecordWrote 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/capturing-screenshots-and-screenrecord)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/capturing-screenshots-and-screenrecord"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/capturing-screenshots-and-screenrecord.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.00215 | $0.03971 |
| Opus 5 | $0.00108 | $0.01985 |
| Sonnet 5 | $0.00043 | $0.00794 |
| Haiku 4.5 | $0.00021 | $0.00397 |
Grade A, and why
capturing-screenshots-and-screenrecord 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capturing Screenshots and screenrecord — Visual Artefacts For Tests
This skill covers grabbing PNG screenshots and MP4 screen recordings from a device through adb, plus the JUnit4 TestWatcher pattern for capturing on test failure. It does not cover Android Studio's screenshot tool, Compose captureToImage(), or third-party streaming tools (scrcpy/Vysor).
When to use this skill
- A flaky CI test needs a screenshot at the moment of failure plus a logcat dump.
- The team generates golden screenshots from a reference device for visual regression.
- QA needs to record a 30 s repro of a bug for a bug report attachment.
- The dev's
adb shell screencap /sdcard/out.pngproduces a corrupt file — the missing-pflag wrote raw RGBA, not PNG. - A Windows CI agent receives screenshots with CRLF corruption — the fix is
adb exec-out screencap -p.
When NOT to use this skill
- Compose-level screenshot tests using
captureToImage()/ Roborazzi / Paparazzi. Those are unit-test mechanisms and live under the Compose set, not ADB. - Continuous live mirroring of the device (presentations, demos). Use scrcpy or Vysor —
screenrecordcannot stream. - Driving the device first (taps, key events). Use
../../control/injecting-input-and-state/SKILL.md. - Pulling files generally (not screenshots). Use
../../transfer/extracting-test-artifacts/SKILL.md.
Prerequisites
adb get-statereturnsdevice. See../../devices/connecting-to-devices/SKILL.md.- For
screenrecord: device API 19+ (Android 4.4) —screenrecordwas added in KitKat. - For
screenrecord+ Wear OS: not supported. The utility refuses (developer.android.com/tools/adb#screenrecord). - For
/sdcard/writes on API 30+: scoped-storage rules apply; theshelluser retains FUSE/sdcardfs access, but app-private writes route through/sdcard/Android/data/<pkg>/.
screencap — PNG screenshots
"The
screencapcommand is a shell utility for taking a screenshot of a device display." — developer.android.com/tools/adb#screencap
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 · 289 lines · 215 tokens per session scan A 13b569d21a74
capturing-screenshots-and-screenrecord is a skill published in the GitHub repository skydoves/android-testing-skills (318 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 215 tokens to every session and 3,971 once invoked, about $0.0011 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_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
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.
agent-device
Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
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.
eas-simulator
EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas…