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 vasilyu1983/AI-Agents-public --skill qa-testing-mobilegit clone --depth 1 https://github.com/vasilyu1983/AI-Agents-publicWrote 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/vasilyu1983/ai-agents-public/qa-testing-mobile)<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/qa-testing-mobile"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/qa-testing-mobile/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/vasilyu1983/ai-agents-public/qa-testing-mobile"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/qa-testing-mobile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 88 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00034 | $0.03314 |
| Opus 5.5 | $0.00014 | $0.01326 |
| Sonnet 5.5 | $0.00007 | $0.00663 |
| Haiku 4.5 | $0.00003 | $0.00331 |
Grade A, and why
qa-testing-mobile 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 19d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Testing (Mobile)
Design and execute reliable, cost-aware mobile testing across iOS and Android (native + cross-platform).
Quick Reference
Start with the workflow; use Expert Judgment for framework and automation tradeoffs, and Resources for depth.
Quick Start
- Fill assets/mobile-test-plan.md to define risk, layers, and gates.
- Fill assets/device-matrix.md from analytics to pick Tier 1/2/3 coverage.
- Use references/framework-comparison.md to choose automation frameworks.
- Use
references/release-and-rollout.mdto define beta, pre-release, staged rollout, and rollback checks. - Use references/accessibility-testing.md to add iOS and Android accessibility coverage.
- Use references/flake-management.md to set a flake budget, reruns, and quarantine rules.
Scope
- Define mobile test strategy across iOS and Android.
- Plan device matrix, OS coverage, and risk tiers.
- Choose automation frameworks and CI + device lab setup.
- Address performance, network/offline, backgrounding, and permissions.
- Define pre-release gates, staged rollout, and store readiness checks.
When NOT to Use
- Platform-specific iOS test command details -> qa-testing-ios
- Platform-specific Android test command details -> qa-testing-android
Inputs to Gather
- Platforms, supported OS versions, and device targets.
- App type (native, cross-platform, hybrid/webview).
- Critical user flows and risk areas.
- Distribution channels and release cadence.
- Beta/release channels (TestFlight, Play internal/closed testing, enterprise distribution if relevant).
- Existing test tooling, CI, and device lab access (Firebase Test Lab, BrowserStack, AWS Device Farm).
- Observability and rollout controls (Crashlytics/Sentry, performance/RUM, feature flags, staged rollout).
- Test data strategy (seed/reset, test accounts, environment parity).
What ships with it
18 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.
- agents/openai.yaml 307 B
- assets/device-matrix.md 2.6 KB
- assets/mobile-test-plan.md 4.8 KB
- assets/release-readiness-checklist.md 4.1 KB
- data/sources.json 18 KB
- learnings.consolidated.md 593 B
- learnings.md 737 B
- references/accessibility-testing.md 1.8 KB
- references/ai-native-testing.md 12 KB
- references/cross-platform-test-patterns.md 19 KB
- references/device-farm-strategies.md 16 KB
- references/flake-management.md 9.7 KB
- references/framework-comparison.md 15 KB
- references/localization-testing.md 1.8 KB
- references/mobile-performance-testing.md 21 KB
- references/release-and-rollout.md 10 KB
- references/test-layers-and-suite-anti-patterns.md 3.6 KB
- references/visual-regression-mobile.md 9.7 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.
- 19d ago Changed · -45 lines · +3 tokens per session 4f142f17b984
- 1mo ago Changed · -1 lines a4128e18b423
- 1mo ago First seen · 221 lines · 31 tokens per session scan A 71a77da40724
qa-testing-mobile is a skill published in the GitHub repository vasilyu1983/AI-Agents-public (101 stars, last pushed 8d ago), licensed MIT. It adds 34 tokens to every session and 3,314 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-09-03.
Other skills, from other repositories
swift-protocol-di-testing
Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.