frogo-sdk: Skill for Claude Code

.agents/skills/android-ui-journey-testing/SKILL.md

android-ui-journey-testing is a skill for Claude Code, Codex from frogobox/frogo-sdk. It costs 27 tokens per session (1,798 once invoked), scanned A, a copy of android-ui-journey-testing, Apache-2.0.

A test runner for Android user journeys, which are ordered sequences of taps, typing, navigation, and expected screen states defined in XML.

In plain words
What is it for?
Testing flows such as login, checkout, and navigation on an Android emulator or device, then producing a JSON results report.
Why use it?
It checks complete app flows consistently instead of relying on slow manual testing, and records whether each step passed or failed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is frogobox/frogo-sdk's own configuration. It tells Claude Code and Codex how to work on frogo-sdk itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything frogo-sdk configures →

Reuse

Borrowing it

Nothing to install: this file belongs to frogobox/frogo-sdk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/frogobox/frogo-sdk/master/.agents/skills/android-ui-journey-testing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/frogobox/frogo-sdk

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.

agentmods badge for android-ui-journey-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/frogobox/frogo-sdk/android-ui-journey-testing.svg)](https://agentmods.dev/skills/frogobox/frogo-sdk/android-ui-journey-testing)
Your own site
<a href="https://agentmods.dev/skills/frogobox/frogo-sdk/android-ui-journey-testing"><img src="https://agentmods.dev/badge/skills/frogobox/frogo-sdk/android-ui-journey-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,798 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 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.01798
Opus 5 $0.00014 $0.00899
Sonnet 5 $0.00005 $0.00360
Haiku 4.5 $0.00003 $0.00180

Measured 6d ago against content hash 0fc3fc750e8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

android-ui-journey-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 6d 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.

Origin

This is a copy

100% identical to android-ui-journey-testing — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/android-ui-journey-testing/SKILL.md · 192 lines

How it starts

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

Android UI Journey Testing

Overview

This skill outlines the standard workflow for running XML-specified User Journey tests on Android applications. A "journey" is a sequenced set of user actions and state assertions designed to verify end-to-end functionality. The journey XML acts as the source of truth for the app's behavior. The executor proceeds sequentially, performing UI interactions, checking state assertions, and writing a standardized JSON outcome report.

When to Use

  • Use when evaluating an Android application's UI behavior against an XML test specification.
  • Use when automating multi-step user flows (e.g., login, checkout, navigation) and verifying expectations.
  • Use when running verification tests and generating standardized JSON test reports.
  • Use when debugging application flows on physical devices or emulators using ADB commands.

How It Works

graph TD
    A[Parse Journey XML] --> B[Execute Action / Interaction]
    B --> C{Success?}
    C -- Yes --> D[Verify State Expectation / Assertion]
    C -- No/Crash --> G[Mark FAILED & Exit]
    D -- Passed --> E{More Steps?}
    D -- Failed --> G
    E -- Yes --> B
    E -- No --> F[Output JSON Summary]

Step 1: Parse the Journey Specification

Read and parse the XML test suite structure. The root node <journey> defines the test case name, and the <actions> block contains the sequence of test steps.

<journey name="Search and Cart Flow">
   <description>Verify that searching for an item and adding it to the cart succeeds.</description>
   <actions>
      <action>Search for soda</action>
      <action>Tap the first search result</action>
      <action>Verify that the product detail screen is shown</action>
   </actions>
</journey>

Step 2: Sequential Step Evaluation

Process each <action> element in the exact order specified. Test steps are classified into two groups:

A. Interactive Actions (Taps, Swipes, Text Input)

Perform the physical UI interaction using ADB.

  • Tapping: Tap the center of the target element's bounds:
    adb shell input tap <x> <y>
    
  • Swiping/Scrolling: Swipe from coordinate to coordinate with a duration:
    adb shell input swipe <x1> <y1> <x2> <y2> <duration_ms>
    
  • Text Typing: Type text into the active input field:
    adb shell input text "<string>"
    

If the element is missing or the action cannot be performed, the action and the journey fail.

Read the full file on GitHub · 192 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.

  1. 6d ago First seen · 192 lines · 27 tokens per session scan A 0fc3fc750e8d

Subscribe to this mod's changes

android-ui-journey-testing is a skill published in the GitHub repository frogobox/frogo-sdk (21 stars, last pushed 4d ago), licensed Apache-2.0. It adds 27 tokens to every session and 1,798 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to android-ui-journey-testing, differing in 0 lines, and is treated as a copy.