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 agentmods add skills/fclab-skku/playwright_for_android/playwright-for-androidnpx skills add fclab-skku/playwright_for_android --skill playwright-for-androidgit clone --depth 1 https://github.com/fclab-skku/playwright_for_androidWrote 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/fclab-skku/playwright_for_android/playwright-for-android)<a href="https://agentmods.dev/skills/fclab-skku/playwright_for_android/playwright-for-android"><img src="https://agentmods.dev/badge/skills/fclab-skku/playwright_for_android/playwright-for-android.svg" alt="Measured on agentmods" 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.00097 | $0.02847 |
| Opus 5 | $0.00048 | $0.01424 |
| Sonnet 5 | $0.00019 | $0.00569 |
| Haiku 4.5 | $0.00010 | $0.00285 |
Grade A, and why
playwright-for-android 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 5d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
playwright-for-android
Tools live in the playwright-for-android MCP server. Each tool's schema (parameters, defaults, descriptions) is authoritative — this document covers only the cross-cutting workflow, reasoning rules, and conventions that don't fit in a single tool description.
When to use
- "Debug the login flow on the emulator and tell me where it breaks."
- "Verify that the new VoiceChat screen renders correctly after I changed
MainActivity.kt." - "Reproduce the FCM-token-staleness logcat error and show me the exact UI step that triggers it."
- "Test the wake-word fallback path on a fresh install."
- Any time the alternative would be juggling
./gradlew,adb install,adb shell am start,adb logcat, and manual UI taps to validate a single feature.
One structured task per invocation. Compose a task, start a session, loop through observations and actions, call finish_test. Surface the returned report to the user. Repeat for the next task.
Driving an app without building it
start_debug_session builds from a Gradle project_root by default. To drive an app this server does not build — e.g. boot the AVD and exercise an already-installed Chrome to test a website — pass skip_build=true. In that mode no Gradle build runs and project_root is not required to be a Gradle project; it only has to be an existing directory, used solely as the run-dir parent (any folder, even a tmp dir, works). gradle_task is ignored.
- Drive an already-installed package:
skip_build=true+skip_install=true(noapk_pathneeded). Setpackageto the app to launch (e.g.com.android.chrome), or addskip_launch=trueto attach without forcing a relaunch. - Install a prebuilt APK without building:
skip_build=true+apk_path=/path/to/app.apk.
Tools at a glance
- Lifecycle:
precheck,start_debug_session,finish_test,abort_session. - Observation:
observe_screen. - Actions (each writes a logcat marker, runs adb, settles, returns the new screen):
tap,long_press,type_text,scroll_dir,scroll_to_text_tool,press_home,press_back,wait.
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.
- 5d ago First seen · 159 lines · 97 tokens per session scan A e8258ac3a8e1
playwright-for-android is a skill published in the GitHub repository fclab-skku/playwright_for_android (3 stars, last pushed 2mo ago), licensed MIT. It adds 97 tokens to every session and 2,847 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-31.
Other skills, from other repositories
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
solopi-ai
通过 SoloPi 的机器可读 CLI 编译和执行 AI 验证计划，管理签名端侧 ExecuTorch 决策模型、持久设备池、无人值守任务、安卓设备、应用、动作、配置、用例步骤与交互录制、回放及性能历史、动态 Agent、批量与重复执行、性能监控、压力测试和证据。适用于需求/AC 到 Result Judge 三态结论、cloud/on-device 决策切换、模型发布门禁，以及 generation 租约的多设备 CI 执行。.
finalrun-use-cli
Use the published FinalRun CLI to install, configure, validate, run, troubleshoot, and inspect reports for repo-local mobile test workspaces. Trigger this skill for requests involving finalrun, check, test, suite, doctor, runs, start-server.
android-ui-test
Demonstration skill showing how to use uiautomator2-mcp-server for AI-driven Android UI testing. Also serves as the project's own automated UI test suite for continuous validation.
android-qa
Test an Android app on a real phone or an emulator using adb. Use when the user wants to install an APK they just compiled, walk through the app's screens, check the on-screen text, reproduce a bug, capture screenshots, read crash logs, or set up an Android testing environment from scratch. Covers both a physical…
mobile-tester
You are the Mobile Tester Specialist. You connect to real Android/iOS devices and write, execute, and report on mobile UI test cases. You master THREE testing modalities.