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 niels-emmer/myace --skill android-testinggit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/android-testing)<a href="https://agentmods.dev/skills/niels-emmer/myace/android-testing"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/android-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/niels-emmer/myace/android-testing"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/android-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.00023 | $0.00326 |
| Opus 5.5 | $0.00009 | $0.00130 |
| Sonnet 5.5 | $0.00005 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
Android 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 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
Purpose
Test Android apps at the right level — fast unit tests for ViewModels, UI tests for critical flows.
Checklist
- Unit tests (JUnit + Robolectric): test ViewModels, repositories, and data transformation logic. Robolectric simulates the Android framework for fast test execution.
- Compose UI tests: use
ComposeTestRuleto test composable rendering and interaction. Cover default, empty, and error states. - Screenshot tests: use
Paparazzior equivalent for Compose screenshot testing. Catch visual regressions. - Espresso tests: for legacy XML-based UI. Don't use for new Compose UI.
- Room DAO tests: use an in-memory Room database instance. Test queries, migrations, and type converters.
- Test independence: each test sets up its own state. Use
StandardTestDispatcher/UnconfinedTestDispatcher(kotlinx-coroutines-test) for coroutine-based code.
Expected output
A test suite where ViewModels are unit-tested with Robolectric, Compose UI is screenshot-tested, and Room DAOs are integration-tested against an in-memory database.
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 · 25 lines · 23 tokens per session scan A 0398e8e5ab00
Android Testing is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 326 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-08-31.
Other skills, from other repositories
loom-test-strategy
Test strategy guidance covering pyramid design, coverage, test categorization, flaky tests, infrastructure, and risk-based prioritization.
loom-testing
Test implementation across unit, integration, e2e, security, infrastructure, data pipeline, and ML domains.
ios-testing
Testing patterns for Swift and SwiftUI apps.
mobile-testing
Android and JVM testing - JUnit5, MockK, Turbine for Flow, and Compose UI testing for unit, integration, and UI tests; also applies to KMP commonTest running on the JVM/Android target. For iOS/Swift tests (XCTest, Swift Testing, XCUITest) use ios-testing. For TDD methodology and the three-tier test model (fake-first…
flutter-testing
A testing guide for Flutter mobile apps and NestJS backends used across multiple regions. It covers unit tests, screen tests, end-to-end tests, regional build variants called flavors, and rules for testing payments, tenants, and external services with test doubles.
flutter-testing
Write, fix, review, debug, and validate Flutter tests for apps, packages, and plugins. Use when adding unit tests, widget tests, integration tests, MethodChannel or plugin mocks, Mockito or mocktail test doubles, golden or accessibility checks, CI test commands, test failures, MissingPluginException, pump or…