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 agents/desquared/agents-rules-skills/android-testing-qa-agentgit clone --depth 1 https://github.com/Desquared/agents-rules-skillsWhat 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 | $0.00052 | $0.00427 |
| Opus 5 | $0.00026 | $0.00214 |
| Sonnet 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 2d 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.
- 2d 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 18d ago), licensed MIT. It adds 52 tokens to every session and 427 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.