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 manykarim/robotframework-agentskills --skill rf-appiumgit clone --depth 1 https://github.com/manykarim/robotframework-agentskillsWrote 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/manykarim/robotframework-agentskills/rf-appium)<a href="https://agentmods.dev/skills/manykarim/robotframework-agentskills/rf-appium"><img src="https://agentmods.dev/badge/skills/manykarim/robotframework-agentskills/rf-appium/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/manykarim/robotframework-agentskills/rf-appium"><img src="https://agentmods.dev/badge/skills/manykarim/robotframework-agentskills/rf-appium.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.00028 | $0.02436 |
| Opus 5.5 | $0.00011 | $0.00974 |
| Sonnet 5.5 | $0.00006 | $0.00487 |
| Haiku 4.5 | $0.00003 | $0.00244 |
Grade A, and why
rf-appium 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AppiumLibrary Skill
AppiumLibrary drives native, hybrid and mobile-web apps on Android and iOS through an Appium 2+ server. Desktop apps belong to rf-platynui; desktop browsers to rf-browser or rf-selenium. Verified against AppiumLibrary 3.2.1, Robot Framework 7.4.
When to use
Load this skill first, before exploring the project or answering from memory, when a Robot Framework test drives a mobile app with AppiumLibrary (Library AppiumLibrary) on Android or iOS:
- writing or fixing a mobile test: Open Application capabilities (UiAutomator2, XCUITest), locators such as
accessibility_id, waits, gestures and scrolling, the on-screen keyboard, WEBVIEW contexts in hybrid apps; - an element cannot be located on a device, or the user mentions Appium, an .apk/.ipa, an emulator or a simulator, even if they only say "our app" or "mobile test".
Not this skill: native desktop apps use rf-platynui; desktop browsers use rf-browser or rf-selenium; installing the Appium server and drivers uses rf-setup.
Installation
Install into the project environment (see rf-setup for uv/venv/Poetry, CI and troubleshooting; follow the project's existing tool):
uv add robotframework-appiumlibrary
The Appium server and platform drivers live outside the Python environment and are installed with npm (requires Node.js):
npm install -g appium
appium driver install uiautomator2 # Android
appium driver install xcuitest # iOS
Android SDK/JDK and Xcode prerequisites: see rf-setup.
Import and defaults
Start the server (appium, default http://127.0.0.1:4723, no /wd/hub base path) before the suite. Default: one session per suite, Android, UiAutomator2, W3C capabilities with the appium: prefix written out:
*** Settings ***
Library AppiumLibrary timeout=15s
Suite Setup Open Android App
Suite Teardown Close All Applications
*** Variables ***
${APPIUM_URL} http://127.0.0.1:4723
*** Keywords ***
Open Android App
Open Application ${APPIUM_URL}
... platformName=Android
... appium:automationName=UiAutomator2
... appium:deviceName=emulator-5554
... appium:app=${CURDIR}/app.apk
... appium:autoGrantPermissions=${True}
What ships with it
9 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.
- assets/examples/android-basic.robot 2.3 KB
- assets/examples/gestures-example.robot 2.4 KB
- assets/examples/hybrid-app.robot 1.9 KB
- assets/examples/ios-basic.robot 1.9 KB
- references/capabilities.md 4.7 KB
- references/gestures-touch.md 4.1 KB
- references/locators-mobile.md 3.9 KB
- references/platform-specific.md 4.8 KB
- references/troubleshooting.md 4.6 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 Changed · -3 tokens per session 3bf67edcca84
- 17d ago First seen · 135 lines · 31 tokens per session scan A 6a5e8bf2a84a
rf-appium is a skill published in the GitHub repository manykarim/robotframework-agentskills (38 stars, last pushed 5d ago), licensed Apache-2.0. It adds 28 tokens to every session and 2,436 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-10-01.
Other skills, from other repositories
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
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.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator 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 iPhone or iPad Simulator.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
eas-simulator
Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to…
flutter-add-widget-test
Implement a component-level test using WidgetTester to verify UI rendering and user interactions (tapping, scrolling, entering text). Use when validating that a specific widget displays correct data and responds to events as expected.