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 FaisalNoman/playwright-skills --skill mobile-app-testinggit clone --depth 1 https://github.com/FaisalNoman/playwright-skillsWrote 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/faisalnoman/playwright-skills/mobile-app-testing)<a href="https://agentmods.dev/skills/faisalnoman/playwright-skills/mobile-app-testing"><img src="https://agentmods.dev/badge/skills/faisalnoman/playwright-skills/mobile-app-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.
<a href="https://agentmods.dev/skills/faisalnoman/playwright-skills/mobile-app-testing"><img src="https://agentmods.dev/badge/skills/faisalnoman/playwright-skills/mobile-app-testing.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.00052 | $0.02853 |
| Opus 5 | $0.00026 | $0.01426 |
| Sonnet 5 | $0.00010 | $0.00571 |
| Haiku 4.5 | $0.00005 | $0.00285 |
Grade A, and why
mobile-app-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 8d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile App Testing (tapflow) Installer
What This Skill Does
Records real-device test flows for your app — web or native — against a self-hosted tapflow relay, using tapflow's own YAML flow format and tapflow flow run CLI — not a custom automation engine. Copies a small report adapter that streams results into an already-installed e2e-dashboard as a new category tab.
Prerequisites (not installed or provisioned by this skill):
- A running tapflow relay + macOS agent (
tapflow start, or a team-operated relay) — see https://www.tapflow.dev/guide/getting-started - The
tapflowCLI available on PATH wherever flows will be run (npm install -g tapflow) - tapflow's MCP server connected to this session (
@tapflowio/mcp-server, see https://www.tapflow.dev/guide/mcp-server) — required only for the recording phase, not for running already-recorded flows - Node.js ≥ 18, for the report adapter script only
- Device matrix is limited to whatever simulators/emulators are booted on the connected Mac agent — tapflow has no cloud device catalog. Testing multiple OS versions means provisioning multiple local runtimes yourself, not picking from a dropdown.
Phase 1 — Discovery & Connectivity
Ask the user in one message:
| Value | How to find | Default |
|---|---|---|
app_type |
Ask directly: "web app or native app?" | none — required |
relay_url |
Ask directly | none — required |
relay_token |
Ask directly (a Personal Access Token from tapflow's Settings → Tokens) | none — required |
app_id |
App identifier used in tapflow flow YAML (appId) — check the project's build config (iOS bundle ID / Android applicationId) or ask |
ask if not found |
flows_dir |
Where flow YAML files live | .tapflow/flows (tapflow's own convention — never relocate under tests/) |
dashboard_installed |
Does a progress-server.js from e2e-dashboard already exist in this project? Glob for **/progress-server.js containing the string E2E Dashboard. |
if absent, skip Phase 4 |
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.
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.
- 8d ago First seen · 134 lines · 52 tokens per session scan A 71dba8f8ec6c
mobile-app-testing is a skill published in the GitHub repository FaisalNoman/playwright-skills (1 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 2,853 once invoked, about $0.0003 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
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…
e2e-testing
AI-powered E2E testing for any app — Flutter, React Native, iOS, Android, Electron, Tauri, KMP, .NET MAUI. Connects via MCP to running apps so the agent can take screenshots, tap elements, enter text, scroll, inspect UI trees, and verify state with natural language. Use when the user wants to test an app's UI…
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.
Espresso Android Testing
Android UI testing with Espresso framework including view matchers, actions, assertions, idling resources, and RecyclerView testing patterns.
ui-aqa-flow
Workflow for automated QA: integration and end-to-end UI test automation, page objects, etc.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.