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 Kokxi/qa-test-skills --skill qa-mobile-testinggit clone --depth 1 https://github.com/Kokxi/qa-test-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/kokxi/qa-test-skills/qa-mobile-testing)<a href="https://agentmods.dev/skills/kokxi/qa-test-skills/qa-mobile-testing"><img src="https://agentmods.dev/badge/skills/kokxi/qa-test-skills/qa-mobile-testing.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00135 | $0.02965 |
| Opus 5 | $0.00068 | $0.01483 |
| Sonnet 5 | $0.00027 | $0.00593 |
| Haiku 4.5 | $0.00014 | $0.00297 |
Grade A, and why
qa-mobile-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 3d 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
移动端测试专项
核心原则
移动测试的核心挑战——设备碎片化、网络不稳定性、用户场景多样性。
移动端测试深度要求（参考值）
| 复杂度 | 用例数要求 | 设备覆盖 |
|---|---|---|
| 简单App | 30条 | 2-3台主流设备 |
| 中等App | 50条 | 5-8台设备 |
| 复杂App | 80条 | 10+台设备+多系统版本 |
必须覆盖的6个维度：
| 维度 | 占比 | 说明 |
|---|---|---|
| 功能测试 | 35% | 核心功能、业务流程 |
| 兼容性测试 | 25% | 设备/系统/屏幕 |
| 中断测试 | 15% | 来电/短信/通知/切换 |
| 性能测试 | 10% | 启动/内存/电量/流量 |
| 弱网测试 | 10% | 网络切换/弱网/离线 |
| 安全测试 | 5% | 权限/数据保护 |
平台专项参考：不同平台有各自的高风险场景，加载对应参考文件可获取专项测试要点：
references/platform-mobile-app.md— iOS/Android 原生 App 专项references/platform-mobile-web.md— H5/移动 Web 专项references/platform-mini-program.md— 小程序专项桌面端 / PC Web 专项不属于本技能范围，如需测试桌面端或 PC Web 请使用通用测试策略技能。
移动端测试检查清单
功能测试检查
- 安装/卸载/升级正常
- 核心功能完整
- 中断测试通过
- 离线功能可用
兼容性测试检查
- 主流设备覆盖
- 系统版本覆盖
- 屏幕尺寸适配
- 横竖屏切换
中断测试检查
- 来电/短信中断
- 通知中断
- 低电量处理
- 网络切换
- 后台/前台切换
性能测试检查
- 启动时间达标
- 内存占用正常
- 帧率流畅
- 电量消耗合理
弱网测试检查
- WiFi/4G切换
- 弱网环境表现
- 离线状态处理
- 网络恢复后同步
功能测试
测试范围：
├─ 安装/卸载/升级
│ ├─ 全新安装
│ ├─ 覆盖安装
│ ├─ 升级安装
│ ├─ 卸载重装
│ └─ 跨版本升级
│
├─ 核心功能
│ ├─ 业务流程测试
│ ├─ 功能交互测试
│ ├─ 数据持久化测试
│ └─ 离线功能测试
│
└─ 中断测试
├─ 来电/短信中断
├─ 通知中断
├─ 低电量中断
├─ 网络切换中断
└─ 后台/前台切换
兼容性测试
设备维度：
├─ 屏幕尺寸：小屏/标准/大屏/折叠屏
├─ 分辨率：720p/1080p/2K/4K
├─ 系统版本：iOS 14+/Android 8+
├─ 设备类型：手机/平板/折叠屏
└─ 品牌厂商：三星/华为/小米/OPPO
系统特性：
├─ 权限管理：不同权限策略
├─ 通知管理：不同通知行为
├─ 后台策略：不同后台限制
└─ 存储策略：不同存储权限
性能测试
性能指标：
├─ 启动时间
│ ├─ 冷启动：<2秒
│ ├─ 热启动：<1秒
│ └─ 温启动：<1.5秒
│
├─ 内存使用
│ ├─ 内存占用：<200MB
│ ├─ 内存泄漏：无持续增长
│ └─ 内存峰值：<300MB
│
├─ 电量消耗
│ ├─ 待机耗电：<5%/天
│ ├─ 使用耗电：<15%/小时
│ └─ 后台耗电：<3%/小时
│
├─ 流量消耗
│ ├─ 首次加载：<5MB
│ ├─ 每次操作：<1MB
│ └─ 后台同步：<10MB/天
│
└─ 帧率
├─ 滑动帧率：>55fps
├─ 动画帧率：>55fps
└─ 页面切换：>50fps
网络测试
网络场景：
├─ 网络类型
│ ├─ WiFi
│ ├─ 4G/5G
│ ├─ 弱网（高延迟、低带宽）
│ └─ 断网
│
├─ 网络切换
│ ├─ WiFi → 4G
│ ├─ 4G → WiFi
│ ├─ 有网 → 断网
│ └─ 断网 → 有网
│
└─ 弱网模拟
├─ 高延迟：>500ms
├─ 低带宽：<100kbps
├─ 高丢包：>10%
└─ 网络抖动：延迟不稳定
What ships with it
5 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.
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.
- 3d ago Changed 7c91a7324361
- 8d ago First seen · 294 lines · 135 tokens per session scan A dcdbd899a79c
qa-mobile-testing is a skill published in the GitHub repository Kokxi/qa-test-skills (24 stars, last pushed 6d ago), licensed MIT. It adds 135 tokens to every session and 2,965 once invoked, about $0.0007 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-30.
Other skills, from other repositories
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
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
EAS service (paid). 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…