Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/skydoves/android-testing-skills/auditing-compose-test-suite)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/auditing-compose-test-suite"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/auditing-compose-test-suite.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.00135 | $0.05294 |
| Opus 5 | $0.00068 | $0.02647 |
| Sonnet 5 | $0.00027 | $0.01059 |
| Haiku 4.5 | $0.00014 | $0.00529 |
Grade A, and why
auditing-compose-test-suite 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auditing a Compose Test Suite — Six-Phase Review, Then Route
This is an index-style skill. It orchestrates the rest of compose-test-skills/ into a fixed-order audit pass over an existing test file or test suite. Each phase produces findings; each finding points at the sibling skill that owns the fix. The audit itself never mutates code — that is the job of the routed skills.
When to use this skill
- The user pastes a
*Test.kt(or several) and asks "what's wrong with this", "review this", "audit this". - The user reports systemic flakes, slow CI, or "the test passes locally but fails on CI".
- The user is preparing a Compose feature for release and wants the test suite vetted.
- The user is migrating from v1 (
UnconfinedTestDispatcher) to v2 (StandardTestDispatcher) and wants a checklist of likely-broken tests. - The user inherited a test file from another team and is unsure what is correct vs accidentally working.
When NOT to use this skill
- The user has a specific failing assertion and wants it fixed — jump directly to the relevant sibling (most often
../../debug/printing-the-semantics-tree/SKILL.mdfor missed matchers, or../../synchronization/testing-animations-deterministically/SKILL.mdfor animation flakes). - The user is starting a brand-new test from scratch — start with
../../setup/configuring-test-dependencies/SKILL.md, then../../setup/choosing-test-rule-vs-runtest/SKILL.md, then../../setup/setting-up-host-vs-device-tests/SKILL.md. - The user wants performance review of production composables — that is
compose-performance-skills, not this repo.
Prerequisites
- Read access to the full test file(s) under review. A single test method is too narrow to audit — patterns emerge across a class.
- The module's
build.gradle.kts(for Phase 1 dep checks) and anysrc/androidTest/AndroidManifest.xmlif the test uses a custom Activity. - Familiarity with the skydoves hot takes encoded in
../docs/SPEC.md§5 (testTag from production, defaultuseUnmergedTree = false,mainClock.autoAdvance = falsefor animations,waitUntilis wall clock,runOnIdlefor state mutations, prefer v2 entry points,Thread.sleepis a smell).
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 · 273 lines · 135 tokens per session scan A 09ecb65231f8
auditing-compose-test-suite is a skill published in the GitHub repository skydoves/android-testing-skills (318 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 135 tokens to every session and 5,294 once invoked, about $0.0007 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…