What is android-screenshot-testing?

Guidance for Android screenshot tests that compare an app's rendered screens with expected images. It covers Paparazzi and Roborazzi, which can run these checks without a physical device or emulator.

Use it to check Jetpack Compose components, Android view hierarchies, and design-system components. It also helps run visual checks in continuous integration and create preview libraries for a design system.

Ordinary tests can miss unintended changes to spacing, colors, or layout. Screenshot comparisons help catch visual differences automatically, including across screen sizes, dark mode, right-to-left layouts, and font scales.

android-screenshot-testing — Skill by prasad-vennam

Install

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.

Any agent

npx skills add prasad-vennam/Awesome-Android-AI-Agent-Skills --skill android-screenshot-testing

Clone the repo

git clone --depth 1 https://github.com/prasad-vennam/Awesome-Android-AI-Agent-Skills

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/prasad-vennam/awesome-android-ai-agent-skills/android-screenshot-testing/github.svg)](https://agentmods.dev/skills/prasad-vennam/awesome-android-ai-agent-skills/android-screenshot-testing)

Your own site

<a href="https://agentmods.dev/skills/prasad-vennam/awesome-android-ai-agent-skills/android-screenshot-testing"><img src="https://agentmods.dev/badge/skills/prasad-vennam/awesome-android-ai-agent-skills/android-screenshot-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/prasad-vennam/awesome-android-ai-agent-skills/android-screenshot-testing"><img src="https://agentmods.dev/badge/skills/prasad-vennam/awesome-android-ai-agent-skills/android-screenshot-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 801 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00028	$0.00801
Opus 5.5	$0.00011	$0.00320
Sonnet 5.5	$0.00006	$0.00160
Haiku 4.5	$0.00003	$0.00080

Measured 2mo ago against content hash 1f45a3afd25d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

android-screenshot-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 2mo 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.

skills/android-screenshot-testing/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Android Screenshot Testing 📸🛡️

Expert techniques for implementing visual regression testing to ensure UI consistency and catch unintended layout changes automatically.

⚡ When to Use

UI Consistency: Verifying complex layouts across screen sizes.
Visual Regression: Catching pixel-level changes in CI/CD.
Design System Audit: Verifying components against design specs.
Screenshot Automation: Generating millions of UI variants (Dark mode, RTL, Font scales).
Test-Driven Design: Testing UI before deploying to devices.

🏗️ Core Tools

1. Paparazzi (Cash App)

Benefit: Runs entirely on the JVM (Host). NO DEVICE/EMULATOR REQUIRED.
Use Case: Testing Jetpack Compose components fast and frequently.
Gradle Task: ./gradlew recordPaparazziDebug / ./gradlew verifyPaparazziDebug

2. Roborazzi (Droidkaigi)

Benefit: Works with Robolectric and provides screenshots in standard unit tests.
Use Case: Testing with existing Robolectric mocks and complex native view hierarchies.

3. Showkase (Airbnb)

Benefit: Auto-generates a library of previews for your app's design system.
Use Case: Creating a "living design system" documentation.

📐 Screenshot Strategy

1. The "Base" Screenshot

Record a "Golden Screenshot" that represents the correct state.
Rule: Commit these screenshots to your repository.

2. Verification (The Diff)

The test compares the current output with the "Golden" version.
Any pixel difference (even 1px) will cause the test to fail.
Use Redline or Side-by-side views to inspect failures.

🚀 Modern Screenshot Workflow

Multi-config Previews: Test every component in:
- Light vs. Dark mode.
- Large font scales (Accessibility).
- RTL (Right-to-Left) languages.
- Different screen densities (ldpi to xxxhdpi).
Data Mocking: Use hardcoded, stable mocks for screenshots (Avoid dynamic dates or network data).
Stable Animations: Disable animations or use FixedTime during screenshot capture to avoid timing issues.

Read the full file on GitHub · 87 lines

Changes

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.

2mo ago First seen · 87 lines · 28 tokens per session scan A 1f45a3afd25d

Subscribe to this mod's changes

android-screenshot-testing is a skill published in the GitHub repository prasad-vennam/Awesome-Android-AI-Agent-Skills (11 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 801 once invoked, about $0.0001 per session on Opus 5.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.

Testing

android-screenshot-testing next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
android-screenshot-testingprasad-vennam/Awesome-Android-AI-Agent-Skills	Skill	11	7mo ago	MIT	A	28	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	today	MIT	A	103	Claude Code