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 traversing-the-semantics-treegit 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/traversing-the-semantics-tree)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/traversing-the-semantics-tree"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/traversing-the-semantics-tree.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.00219 | $0.03350 |
| Opus 5 | $0.00110 | $0.01675 |
| Sonnet 5 | $0.00044 | $0.00670 |
| Haiku 4.5 | $0.00022 | $0.00335 |
Grade A, and why
traversing-the-semantics-tree 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 7d 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Traversing the Semantics Tree — When a Single Finder Won't Reach the Node
The single-finder shortcuts (onNodeWithTag, etc.) cover ~95% of test queries. The remainder need tree navigation: "the parent of this Text", "the third child of this Row", "any sibling that is enabled". This skill maps those navigation operators, calls out the LazyColumn snapshot caveat, and shows when traversal is the wrong tool.
When to use this skill
- The target node has no stable
testTagand one cannot be added to production (third-party composable, dynamically generated children). - The test verifies structural relationships ("the second child of the row is the icon").
- The developer chains
.onChildren()[i].onChildAt(j)and wants to know whether that is the right shape. - The developer mentions
onChildren,onChild,onParent,onSibling,onSiblings,onAncestors,filterToOne,onFirst,onLast, or[index]. - A
LazyColumntest misses items because they are off-screen.
When NOT to use this skill
- A
Modifier.testTag(...)could be added to the target node — adding a tag is almost always cleaner than a traversal chain. See../finding-nodes-by-tag-text-content/SKILL.md. - The relationship is "anywhere above" / "anywhere below" — prefer the matcher-based
hasAnyAncestor/hasAnyDescendant(see../composing-semantics-matchers/SKILL.md). - The query is about a LazyColumn item by key — use
performScrollToKeyinstead (see../../actions/clicking-and-scrolling/SKILL.md,../../patterns/testing-lazy-lists/SKILL.md).
Prerequisites
- A working
ComposeTestRule/ComposeUiTest. See../../setup/configuring-test-dependencies/SKILL.md. - Familiarity with the merged vs unmerged tree distinction. See
../finding-nodes-by-tag-text-content/SKILL.md.
Workflow
- 1. Pick the navigator by relationship type. Each operator returns either a
SemanticsNodeInteraction(single — fails on 0 or >1) or aSemanticsNodeInteractionCollection(plural — never fails on 0).
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.
- 7d ago First seen · 254 lines · 219 tokens per session scan A 7dfc4e46e53a
traversing-the-semantics-tree is a skill published in the GitHub repository skydoves/android-testing-skills (318 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 219 tokens to every session and 3,350 once invoked, about $0.0011 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
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
eas-simulator
EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas…
flutter-add-integration-test
Configures Flutter Driver for app interaction and converts MCP actions into permanent integration tests. Use when adding integration testing to a project, exploring UI components via MCP, or automating user flows with the integrationtest package.