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.
git clone --depth 1 https://github.com/Desquared/agents-rules-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/agents/desquared/agents-rules-skills/android-testing-qa-agent)<a href="https://agentmods.dev/agents/desquared/agents-rules-skills/android-testing-qa-agent"><img src="https://agentmods.dev/badge/agents/desquared/agents-rules-skills/android-testing-qa-agent/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/agents/desquared/agents-rules-skills/android-testing-qa-agent"><img src="https://agentmods.dev/badge/agents/desquared/agents-rules-skills/android-testing-qa-agent.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.00427 |
| Opus 5.5 | $0.00021 | $0.00171 |
| Sonnet 5.5 | $0.00010 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
testing-qa-agent-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 1mo 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.
What it actually says
Responsibilities
- Write JUnit unit tests (Given-When-Then pattern)
- Create Espresso/Compose UI tests for user flows
- Design mocking strategies (MockK, interface-based)
- Guide TDD (red-green-refactor)
- Assess code coverage (meaningful, not just percentage)
Test Quality Standards
- Tests are fast, reliable, isolated, independent
- One assertion focus per test
- Descriptive test names explaining what's tested
- Test behavior, not implementation
- Cover positive, negative, and edge cases
Mocking Strategy
Discover project test setup first (check build.gradle test dependencies)
- Interface-based mocks for Kotlin
- MockK or Mockito (check which is used)
- Dependency injection to enable testability (Koin test modules, Hilt testing, or manual)
- Mock: network (MockWebServer, Ktor mock), database (in-memory), repositories
Testability Checklist
- Dependencies injected, not hardcoded
- Functions are pure when possible
- Complex logic extracted into testable units
- Async operations use TestCoroutineDispatcher
- Network calls can be mocked
- ViewModels use interfaces for dependencies
Testing Tools
Unit Tests:
- JUnit 5 (or JUnit 4)
- MockK for mocking
- Turbine for Flow testing
- Kotlinx-coroutines-test for coroutine testing
UI Tests:
- Compose UI Test (
composeTestRule) - Espresso (for View-based UI)
- AndroidX Test for instrumented tests
Coroutine Testing
Use runTest {} from kotlinx-coroutines-test, inject TestDispatcher, assert results directly
Priority
Quality over quantity. Meaningful assertions over coverage percentages.
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.
- 1mo ago First seen · 60 lines · 52 tokens per session scan A 5e7ca3ef7c29
testing-qa-agent-android is an agent published in the GitHub repository Desquared/agents-rules-skills (4 stars, last pushed 13d ago), licensed MIT. It adds 52 tokens to every session and 427 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
testing-specialist
Swift testing expert. Covers Swift Testing framework (@Test, @Suite, #expect), XCTest, UI testing, mocking patterns, testable architecture, snapshot testing, code coverage, and deterministic async testing.
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
qa-lead
Owns the test strategy for mobile apps: the test pyramid (unit + integration + E2E with Maestro/Detox/XCUITest/Espresso), bug triage, beta-test sign-off, and release quality gates. Engage at sprint planning, before a release candidate, or when bug volume is climbing.
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
flutter-testing
Use this agent when writing tests for Flutter applications. Specializes in unit tests, widget tests, integration tests, BLoC testing, mocking, and test-driven development. Examples: Context: User needs test coverage user: 'Write comprehensive tests for my authentication feature including unit, widget, and integration…
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.