Roborazzi is an Android testing tool that captures screenshots from JVM tests using Robolectric, which simulates Android framework behavior on a developer’s computer. It helps teams check an app’s visual appearance and interactions without relying solely on physical devices or emulators. The catalogue skill supports using Roborazzi for screenshot-based Android testing.
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 takahirom/roborazzi --skill roborazzigit clone --depth 1 https://github.com/takahirom/roborazziWrote 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/takahirom/roborazzi/roborazzi)<a href="https://agentmods.dev/skills/takahirom/roborazzi/roborazzi"><img src="https://agentmods.dev/badge/skills/takahirom/roborazzi/roborazzi/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/takahirom/roborazzi/roborazzi"><img src="https://agentmods.dev/badge/skills/takahirom/roborazzi/roborazzi.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00095 | $0.00912 |
| Opus 5 | $0.00048 | $0.00456 |
| Sonnet 5 | $0.00019 | $0.00182 |
| Haiku 4.5 | $0.00010 | $0.00091 |
Grade A, and why
roborazzi 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.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roborazzi
Roborazzi is a screenshot testing library for Android that runs on the JVM using Robolectric Native Graphics, so screenshot tests run as JVM unit tests without a device or emulator. It works with plain Android views, Jetpack Compose (including Compose Previews), and Compose Multiplatform.
The typical workflow: record baseline images with ./gradlew recordRoborazziDebug, then compare or
verify against them with compareRoborazziDebug / verifyRoborazziDebug (task names vary by
variant; see the build setup reference).
Reference index
Read the reference that matches the task at hand:
| File | Read when |
|---|---|
| references/top.md | You need an overview of what Roborazzi is and why to use it over device tests or Paparazzi. |
| references/try_it_out.md | You want a minimal quick start or a sample project to try Roborazzi. |
| references/build_setup.md | Setting up the Gradle plugin and dependencies, or running/understanding the record/compare/verify Gradle tasks and their outputs. |
| references/how_to_use.md | Writing tests: captureRoboImage for views/Compose/Espresso, RoborazziRule and its options, output paths and file naming, RoborazziOptions (thresholds, image comparators, dump mode). |
| references/gif_and_video.md | Capturing GIFs and videos of test interactions: captureRoboGif, recordRoboVideo / recordScreenRoboVideo, RoboVideoOptions, GIF vs APNG output. |
| references/ui_tree_dump.md | UI tree dump: the machine-readable .uitree.json semantics sidecar and annotated Set-of-Mark image for tools & AI agents (roborazzi.dumpUiTree, uiTreeDumpOptions), including the verify-a-UI-fix-by-bounds workflow. |
| references/github_actions.md | Setting up GitHub Actions CI for Roborazzi: workflows that store baseline screenshots, verify them, and compare snapshot results on pull requests. |
| references/preview_support.md | Generating screenshot tests from @Preview composables with ComposablePreviewScanner, including setup and customization of preview tests. |
| references/compose_multiplatform.md | Screenshot testing Compose Multiplatform targets (iOS, desktop/JVM), including feature support per platform. |
| references/ai_powered_image_assertion.md | Asserting screenshot content with AI models (OpenAI, Gemini) via roborazzi-ai modules. |
| references/gradle_properties_options.md | Configuring roborazzi.* Gradle properties: task behavior, output directory, file-name strategy, comparison report settings. |
| references/idea_plugin.md | Using the Roborazzi IntelliJ IDEA / Android Studio plugin to view screenshots in the IDE. |
| references/faq.md | Troubleshooting: common errors, CI setup questions, Robolectric configuration issues, and other frequently asked questions. |
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/ai_powered_image_assertion.md 4.9 KB
- references/build_setup.md 7.5 KB
- references/compose_multiplatform.md 6.9 KB
- references/faq.md 6.1 KB
- references/gif_and_video.md 7.1 KB
- references/github_actions.md 3.3 KB
- references/gradle_properties_options.md 3.7 KB
- references/how_to_use.md 8.6 KB
- references/idea_plugin.md 778 B
- references/preview_support.md 16 KB
- references/top.md 2.8 KB
- references/try_it_out.md 758 B
- references/ui_tree_dump.md 5.1 KB
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 · 40 lines · 95 tokens per session scan A cde459714fad
roborazzi is a skill published in the GitHub repository takahirom/roborazzi (1,035 stars, last pushed 3d ago), licensed Apache-2.0. It adds 95 tokens to every session and 912 once invoked, about $0.0005 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
ios-testing
Testing patterns for Swift and SwiftUI apps.
mobile-testing
Android and JVM testing - JUnit5, MockK, Turbine for Flow, and Compose UI testing for unit, integration, and UI tests; also applies to KMP commonTest running on the JVM/Android target. For iOS/Swift tests (XCTest, Swift Testing, XCUITest) use ios-testing. For TDD methodology and the three-tier test model (fake-first…
cmp-qa-prep
Bring up the E2E harness for a Kotlin/Compose Multiplatform app — boot the Android emulator, install the debug build, run the Maestro smoke — or, simpler, run the verify lane, which does all three itself. Use this when the user wants to run E2E/device tests on their CMP/KMP app, "prep my KMP test environment", "smoke…
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.