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/GuillemRoca/agent-skills-androidWrote 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/commands/guillemroca/agent-skills-android/test)<a href="https://agentmods.dev/commands/guillemroca/agent-skills-android/test"><img src="https://agentmods.dev/badge/commands/guillemroca/agent-skills-android/test/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/commands/guillemroca/agent-skills-android/test"><img src="https://agentmods.dev/badge/commands/guillemroca/agent-skills-android/test.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.00000 | $0.00453 |
| Opus 5.5 | $0.00000 | $0.00181 |
| Sonnet 5.5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
test 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
/test — Test-Driven Development
Write tests before implementation using Red-Green-Refactor.
Instructions
Load and follow these skills:
test-driven-developmentfromskills/test-driven-development/SKILL.mdandroid-device-testingfromskills/android-device-testing/SKILL.md(for instrumented tests)android-e2e-verificationfromskills/android-e2e-verification/SKILL.md(for end-to-end acceptance flows)
New Feature Testing
- Write failing test describing the expected behavior
- Run test — confirm it FAILS (RED)
- Write minimal code to make it pass (GREEN)
- Run full suite —
./gradlew test - Refactor while tests stay green
- Repeat for next behavior
Bug Fix Testing (Prove-It Pattern)
- Write a test that demonstrates the bug
- Run test — confirm it FAILS (proves bug exists)
- Fix the code
- Run test — confirm it PASSES (proves fix works)
- Run full suite —
./gradlew test(no regressions)
Test Types
| Type | Framework | Command |
|---|---|---|
| Unit tests | JUnit5 + MockK | ./gradlew test |
| Compose UI tests | Compose test rules | ./gradlew connectedAndroidTest |
| Espresso tests | Espresso | ./gradlew connectedAndroidTest |
| Room DAO tests | In-memory Room | ./gradlew connectedAndroidTest |
| Screenshot tests | Preview Screenshot Testing / Roborazzi | ./gradlew validateDebugScreenshotTest |
| E2E acceptance flows | Maestro | maestro test .maestro/ |
Rules
- Tests BEFORE implementation (always)
- Every test must be seen failing before passing
- No
Thread.sleep— useadvanceUntilIdle()orwaitUntil - Mock at boundaries only (DAO, API), not internal classes
- Descriptive test names that read like behavior specs
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 · 47 lines · 0 tokens per session scan A e70417f26def
test is a command published in the GitHub repository GuillemRoca/agent-skills-android (3 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 453 tokens. 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 commands, from other repositories
9_gofer_tests
Generate comprehensive test suites from four testing perspectives for a target component.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.
test
Run, author, or set up tests: run and repair, QA pass, TDD, Playwright E2E, coverage gates, or CI init.
gofer:tdd
Guide a red-green-refactor loop tied to spec acceptance criteria.
implement
E2E-first Test driven development — unit tests written last.
ui-test
Run VIOS UI tests using the playwright plugin.