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 skydoves/android-testing-skills --skill asserting-node-state-and-textgit clone --depth 1 https://github.com/skydoves/android-testing-skillsWrote 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/asserting-node-state-and-text)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/asserting-node-state-and-text"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/asserting-node-state-and-text/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/skydoves/android-testing-skills/asserting-node-state-and-text"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/asserting-node-state-and-text.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00220 | $0.03634 |
| Opus 5.5 | $0.00088 | $0.01454 |
| Sonnet 5.5 | $0.00044 | $0.00727 |
| Haiku 4.5 | $0.00022 | $0.00363 |
Grade A, and why
asserting-node-state-and-text 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.
How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Asserting Node State and Text — Verify Through the Framework, Not Through fetchSemanticsNode
Once a finder resolves to a SemanticsNodeInteraction, the next step is asserting it. Compose ships a typed assertion for almost every semantic property; the generic assert(matcher) covers the rest. This skill picks the right assertion, distinguishes "exists" from "displayed", and shows when boolean predicates belong inside waitUntil.
When to use this skill
- The developer wants to verify a Switch is on, a Checkbox is unchecked, a Button is enabled, a Text equals an expected string.
- The developer asks about
assertIsDisplayedvsassertExists(one verifies on-screen, the other verifies presence in the tree). - The developer needs a custom assertion via
assert(matcher)for a property without a typed extension. - The developer wants to verify a collection: "exactly 3 items", "at least one is selected", "all are enabled".
- A test compares
node.config[...]directly instead of using a typed assertion.
When NOT to use this skill
- The right node cannot be located — see
../../finders/finding-nodes-by-tag-text-content/SKILL.md. - The assertion is geometric (width, height, position) — see
./asserting-bounds-and-dimensions/SKILL.md. - The check needs a custom
SemanticsMatcher— see../../finders/composing-semantics-matchers/SKILL.md. - The state changes asynchronously and the assertion is timing-sensitive — see
../../synchronization/synchronizing-with-idle/SKILL.md.
Prerequisites
- A working
ComposeTestRule/ComposeUiTest. See../../setup/configuring-test-dependencies/SKILL.md. - The node has been located through
onNode*/onAllNodes*/ a navigator. - For
assertIsDisplayedsemantics, the node must be composed AND placed AND at least partially on-screen post-clip (Assertions.kt:30-39).
Workflow
- 1. Pick by question type. Map the developer's question to one assertion call. Every API listed is in
commonMain/.../Assertions.ktunless noted.
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 · 237 lines · 220 tokens per session scan A 70381468b5b1
asserting-node-state-and-text is a skill published in the GitHub repository skydoves/android-testing-skills (337 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 220 tokens to every session and 3,634 once invoked, about $0.0009 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-30.
Other skills, from other repositories
swift-protocol-di-testing
Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.
android-do-not-mock
How to write (or fix) Chromium Java unit tests (Robolectric / JUnit) without mocking or spying android.view.View, android.app.Activity, or their subclasses. Use when removing @SuppressWarnings("DoNotMock"), fixing a "DoNotMock" Error Prone error, replacing Mockito.mock(View.class) / @Mock Activity / spy(view), or when…
android-unit-test
Guide for writing and converting Chromium Android unit tests across host Robolectric (chromejunittests) and on-device (chromepublicunittestapk) suites.
react-native-testing
Write tests using React Native Testing Library (RNTL) v13 and v14 (@testing-library/react-native). Use when writing, reviewing, or fixing React Native component tests. Covers: render, screen, queries (getBy/getAllBy/queryBy/findBy), Jest matchers, userEvent, fireEvent, waitFor, and async patterns. Supports v13 (React…
flutter-add-widget-test
Implement a component-level test using WidgetTester to verify UI rendering and user interactions (tapping, scrolling, entering text). Use when validating that a specific widget displays correct data and responds to events as expected.
flutter-testing-skill
Generates Flutter widget tests, integration tests, and golden tests in Dart. Supports local execution and TestMu AI cloud for real device testing. Use when user mentions "Flutter", "widget test", "WidgetTester", "testWidgets", "fluttertest", "integrationtest". Triggers on: "Flutter", "widget test", "Dart test"…