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.
Borrowing it
Nothing to install: this file belongs to takahirom/roborazzi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/takahirom/roborazzi/main/AGENTS.mdgit 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/instructions/takahirom/roborazzi/agents-md)<a href="https://agentmods.dev/instructions/takahirom/roborazzi/agents-md"><img src="https://agentmods.dev/badge/instructions/takahirom/roborazzi/agents-md/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/instructions/takahirom/roborazzi/agents-md"><img src="https://agentmods.dev/badge/instructions/takahirom/roborazzi/agents-md.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.00777 | $0.00777 |
| Opus 5.5 | $0.00311 | $0.00311 |
| Sonnet 5.5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
roborazzi AGENTS.md 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 17d 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 — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI coding agents working on Roborazzi. For build setup, project structure, and how to run tests, read CONTRIBUTING.md first.
Adding or changing public API
Roborazzi is a library, so anything public is hard to change later. That includes Gradle properties, the Gradle DSL, and IDs shown in messages, not only Kotlin API. Before adding public API, check each point below. In the PR description, say how the change handles each one.
- Fits in with its neighbours. Look at the properties, parameters, and functions next to where you are adding it. Check that its name, parameter order, and default look like theirs and nothing stands out. When the same feature also appears in the Gradle DSL,
gradle.properties, Kotlin API, or docs, use the same name in every place. Name it after what users see there, not after where the code runs (plugin, library, test JVM), which may change. - Has a home to grow in. Put a new setting in the options class for its area, not directly on
RoborazziOptions. If there is no such class, consider adding one: a blur setting, for example, would go in a rendering options class, so the next rendering setting has a place too. - Can change without breaking callers. Don't use a
data classfor new public types: adding a property changes its constructor andcopy(), which breaks binary compatibility. If a type needsequals/hashCode/toString, annotate a plain class with@Poko(Roborazzi's own marker inroborazzi-core). If new kinds are likely, prefer aninterfaceover anenum class. - Hard to misuse. Avoid adjacent parameters of the same type that still compile when swapped. Validate in
initand fail early with a message that includes the bad value. - Marked
@ExperimentalRoborazziApiwhen in doubt. This is the norm for new features here.
Then run ./gradlew apiDump (and cd include-build && ./gradlew apiDump), commit the api/*.api files, and read the diff. Every removed or changed line is a potential binary break. Restore it with a @Deprecated(level = DeprecationLevel.HIDDEN) bridge, or call it out in the PR.
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.
- 17d ago First seen · 26 lines · 777 tokens per session scan A 360b5d7f8a10
roborazzi AGENTS.md is an instructions file published in the GitHub repository takahirom/roborazzi (1,064 stars, last pushed yesterday), licensed Apache-2.0. It adds 777 tokens to every session, about $0.0031 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-10-05.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.