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 skills/gdvega/super-android-kotlin-firebase-skill/testingnpx skills add GDvega/super-android-kotlin-firebase-skill --skill testinggit clone --depth 1 https://github.com/GDvega/super-android-kotlin-firebase-skillWrote 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/gdvega/super-android-kotlin-firebase-skill/testing)<a href="https://agentmods.dev/skills/gdvega/super-android-kotlin-firebase-skill/testing"><img src="https://agentmods.dev/badge/skills/gdvega/super-android-kotlin-firebase-skill/testing.svg" alt="Measured on agentmods" 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.00034 | $0.00652 |
| Opus 5 | $0.00017 | $0.00326 |
| Sonnet 5 | $0.00007 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
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 6d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Create high-value tests with low fragility across Android layers.
When to use
- Adding or reviewing tests.
- Testing ViewModels, Flow or coroutines.
- Testing Compose UI or accessibility.
- Testing Firebase rules/functions with Emulator Suite.
Inputs to inspect
- Behavior under test.
- Existing test dependencies and source sets.
- Repository fakes or data builders.
- Gradle tasks and CI constraints.
Required workflow
- Choose the lowest useful test level first.
- Create fakes for behavior-focused tests.
- Use coroutine test APIs and virtual time.
- Add Compose UI/instrumented tests only for critical flows.
- Run the relevant Gradle task and report results.
Rules
- No Thread.sleep.
- Prefer fakes over mocks when state transitions matter.
- Test loading, success, empty, error and permission-denied states.
- Use Firebase Emulator for rules when available.
- Keep UI tests focused.
Related existing skills
Local skills to invoke
- debugging
- gradle-build
- firebase-emulator-ci
- jetpack-compose
- code-review-refactor
External companion skills to use when installed
Do not assume these companion skills are installed. Prefer the local skills above first, then consult Companion Skills for install and verification commands.
- skydoves/android-testing-skills — use for deeper Android or Compose UI testing, semantics, assertions or test workflow guidance.
- android/skills — use for official Android workflow alignment around edge-to-edge, adaptive UI, Navigation 3, R8, AGP or testing setup.
Files commonly touched
src/testsrc/androidTestViewModel testsrepository testsCompose testsrules tests
Commands to validate
./gradlew test
./gradlew connectedDebugAndroidTest
./gradlew lint
firebase emulators:exec "npm test"
adb logcat
Common mistakes to avoid
- Only testing happy path.
- Using UI tests for pure logic.
- Over-mocking repositories.
- Ignoring source set setup.
What ships with it
3 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.
- 6d ago First seen · 106 lines · 34 tokens per session scan A 54c2d3a3f159
testing is a skill published in the GitHub repository GDvega/super-android-kotlin-firebase-skill (2 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 652 once invoked, about $0.0002 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 skills, from other repositories
test-flutter
Flutter App のテスト実行・静的解析・フォーマット・テスト記述ガイド.
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
Flutter + NestJS 多区域项目测试规范 — Flutter 单元测试（Notifier/Provider + ProviderContainer override）、widget 测试、golden 测试、★ flavor 条件编译测试（cn 不含 Firebase / overseas 不含 JPush 的静态与运行时验证）、多租户隔离测试、AI 扣费 refund 测试、NestJS service 单测（mock Prisma）、e2e（supertest + 测试库）、mocktail/jest mock 约定、覆盖率门禁。.
Android Testing
JUnit + Robolectric unit tests, Compose UI tests, screenshot tests, and Espresso for legacy views.
cometchat-native-testing
Testing patterns for CometChat React Native — Jest + React Native Testing Library setup, mocking the UI Kit + SDK, testing custom bubbles / headers / composer actions, snapshot pitfalls, E2E with Detox vs Maestro, and CI integration. Covers what to test vs what to skip.