A guide for creating and running Maestro end-to-end tests for React Native apps. It covers written user flows, test timing, test identifiers, multiple devices, network simulation, and app-state checks.

Use it to write UI tests, create end-to-end flows, add test identifiers, run tests, verify features, simulate network responses, inspect stored app state, and write assertions.

It helps tests behave like real user interactions and avoids treating a screen produced by injected state as proof that the journey works.

rn-testing — Skill for Claude Code by Lykhoyda/rn-dev-agent

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 Lykhoyda/rn-dev-agent --skill rn-testing

Clone the repo

git clone --depth 1 https://github.com/Lykhoyda/rn-dev-agent

Made for: Claude Code.

Or install rn-dev-agent, the plugin that ships this one along with the rest of its 28 skills, 17 commands, 6 agents, 6 hooks.

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/lykhoyda/rn-dev-agent/rn-testing/github.svg)](https://agentmods.dev/skills/lykhoyda/rn-dev-agent/rn-testing)

Your own site

<a href="https://agentmods.dev/skills/lykhoyda/rn-dev-agent/rn-testing"><img src="https://agentmods.dev/badge/skills/lykhoyda/rn-dev-agent/rn-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/lykhoyda/rn-dev-agent/rn-testing"><img src="https://agentmods.dev/badge/skills/lykhoyda/rn-dev-agent/rn-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 4,974 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. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Rogue Agent · line 3
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.

Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
medium Data Exfiltration · line 420
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.

How audits are shown

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.00106	$0.04974
Opus 5.5	$0.00042	$0.01990
Sonnet 5.5	$0.00021	$0.00995
Haiku 4.5	$0.00011	$0.00497

Measured 19d ago against content hash 731d06467e07, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rn-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 19d 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.

packages/claude-plugin/codex-skills/rn-testing/SKILL.md · 499 lines

How it starts

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

rn-testing — Maestro Patterns, Timing Rules, and Test Strategy

How to write and run UI test flows for React Native feature verification. Covers test runner selection, timing rules, testID conventions, multi-device testing, network mocking, and store inspection setup.

Test Runner: maestro-runner floor (>= 1.1.27)

All YAML replay goes through rn-dev-agent's maestro_run, cdp_run_action, or cdp_run_e2e_suite tools. They require maestro-runner >= 1.1.27 from the versioned pin-cache (attested 1.1.27 is the default known-good) and refuse missing, older, unverified, or checksum-mismatched binaries before UI mutation.

node <plugin-root>/rn-dev-agent-core/dist/maestro-runner-pin.js diagnose --json
bash <plugin-root>/scripts/ensure-maestro-runner.sh
node <plugin-root>/rn-dev-agent-core/dist/maestro-runner-pin.js diagnose --json

Success requires pinned-ok, version >= 1.1.27, provenance pin-cache, and the versioned selected path. Never resolve replay from PATH, ~/.maestro-runner, or another CLI.

Verification Fidelity — No Silent Shortcuts (#61)

Verification means simulating a real user. State injection that produces a matching screen is NOT verification.

The following count as shortcuts that invalidate verification unless the user explicitly sanctions them:

Deep-linking past the entry point of the flow being verified (e.g. deep-linking to success-details/<existingId> instead of walking the create flow).
Forcing route params a real user can't set (e.g. isNewPolicy=true, fromSuccess=true, mode=edit injected via URL).
Writing to MMKV / AsyncStorage / SecureStore to reset cooldowns, permissions, "has-seen" flags, or session state.
Dispatching Redux / Zustand actions directly rather than through UI (cdp_dispatch from outside a real user gesture).
Calling native-module APIs to skip platform dialogs (e.g. faking permission grants, dismissing system prompts via JS).

These tools work equally well from inside a real flow and as state injection — the plugin can't tell the difference. The agent is the safeguard.

Read the full file on GitHub · 499 lines

Files

What ships with it

1 file 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/network-mocking-setup.md 2.4 KB

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.

19d ago Changed 731d06467e07
27d ago Changed 47613b46b46f
1mo ago Changed 7c55e6947213
1mo ago First seen · 499 lines · 106 tokens per session scan A 1769b7dc6a8a

Subscribe to this mod's changes

rn-testing is a skill published in the GitHub repository Lykhoyda/rn-dev-agent (20 stars, last pushed today), licensed MIT. It adds 106 tokens to every session and 4,974 once invoked, about $0.0004 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-30.

E2E testing Mobile Testing agent agent-framework agent-orchestration agentic-ai agentic-workflow agents

run-dashboard-e2e-local-changes

Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.

BlackBeltTechnology/pi-agent-dashboard · 42 tokens

pod-e2e

ONLY for developing Kiro Crew itself -- if the project you are working on is anything else, ignore this skill: it drives Kiro Crew's own pod tooling, which does not exist in another repository. Boots a Kiro Crew feature worktree's full stack as an ISOLATED throwaway pod and proves it boots, authenticates and renders…

kirodotdev/KiroCrew · 174 tokens

android-emulator

Verify and debug native, React Native, Expo, or Flutter apps on an Android Emulator 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 Android virtual device.

callstack/agent-device · 65 tokens

rn-testing