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 printing-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/printing-the-semantics-tree)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/printing-the-semantics-tree"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/printing-the-semantics-tree.svg" alt="Measured on agentmods" 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.00061 | $0.03143 |
| Opus 5 | $0.00030 | $0.01571 |
| Sonnet 5 | $0.00012 | $0.00629 |
| Haiku 4.5 | $0.00006 | $0.00314 |
Grade A, and why
printing-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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Printing the Semantics Tree — When a Finder Fails, Dump the Tree
onNodeWithTag failures are structural — the tag is wrong, the matcher is on the merged tree but the tag is on a leaf, or the node is genuinely not composed yet. None of those are timing problems, so Thread.sleep does nothing. This skill teaches the agent to diagnose finder failures by dumping the semantics tree with printToLog / printToString and reading the framework's built-in "found in the unmerged tree" hint.
When to use this skill
- The test fails with
"Failed: assertExists. Reason: Expected exactly '1' node but could not find any node that satisfies: …". - The test fails with
"Reason: Expected exactly '1' node but found 'N' nodes that satisfy: …". - The error message ends with
"…were found in the unmerged tree. If you really wanted to match against merged tree, use useUnmergedTree = true."and the developer is confused. - The developer is writing a custom matcher and needs direct access to a
SemanticsNode. - A test was fixed by adding
Thread.sleep— the underlying problem is a wrong tag, not a timing issue. Replace with this skill's pattern. See skydoves directive #7.
When NOT to use this skill
- The symptom is timing (animation has not finished, an idling resource is busy). Use
../../synchronization/synchronizing-with-idle/SKILL.mdor../../synchronization/testing-animations-deterministically/SKILL.md. - The finder is wrong because the test searches by text instead of by tag. Fix with
../../finders/finding-nodes-by-tag-text-content/SKILL.md(skydoves directive #1). - The diagnosis involves accessibility violations rather than node lookup. Use
../enabling-accessibility-checks/SKILL.md.
Prerequisites
androidx.compose.ui:ui-testonandroidTestImplementationortestImplementation(the API lives incommonMainso it is available in both source sets).- An active
ComposeTestRuleorComposeUiTest(no extra setup beyond the standard skeleton).
Workflow
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 · 223 lines · 61 tokens per session scan A afab166b3a16
printing-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 61 tokens to every session and 3,143 once invoked, about $0.0003 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
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.