Borrowing it
Nothing to install: this file belongs to parawanderer/OpenTagViewer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/parawanderer/OpenTagViewer/main/.claude/skills/watch-gradle-tests/SKILL.mdgit clone --depth 1 https://github.com/parawanderer/OpenTagViewerWrote 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/parawanderer/opentagviewer/watch-gradle-tests)<a href="https://agentmods.dev/skills/parawanderer/opentagviewer/watch-gradle-tests"><img src="https://agentmods.dev/badge/skills/parawanderer/opentagviewer/watch-gradle-tests/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/parawanderer/opentagviewer/watch-gradle-tests"><img src="https://agentmods.dev/badge/skills/parawanderer/opentagviewer/watch-gradle-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 61 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00045 | $0.00959 |
| Opus 5 | $0.00023 | $0.00479 |
| Sonnet 5 | $0.00009 | $0.00192 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
watch-gradle-tests 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 11d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Watching a test run to a verdict
The emulator suite takes upwards of ten minutes, so it gets backgrounded, so something has to report on it. Do not write that something fresh each time. Use the script.
# 1. Start the run, redirected to a file.
./gradlew :app:testEmulatorDebugAndroidTest --console=plain > tmp/run.log 2>&1
# 2. Prove the watcher sees the log before trusting it. One command, always.
python .claude/skills/watch-gradle-tests/watch_tests.py tmp/run.log --once
# 3. Arm a Monitor on the same script with no --once.
python .claude/skills/watch-gradle-tests/watch_tests.py tmp/run.log
Each line it prints is one event: FAILED <Class>.<method> as each failure appears,
STALLED … if the log stops growing, and FINISHED + VERDICT at the end.
Why this exists
Three hand-written monitors in one afternoon each matched nothing, and each looked like a green run:
| What was written | Why it matched nothing |
|---|---|
grep "(0 skipped)" |
the run had 5 skipped |
grep "\S+ \[testEmulator\]" |
there is no space before [testEmulator] |
... | head -25 |
truncated before the verdict, and head's exit code hid it |
All three exited 0. Silence from a monitor is indistinguishable from silence from a healthy
run, so a red suite was reported as green until the log was read by hand. That is the whole
argument for a script: the patterns get fixed once, and --once proves they still match before
anything depends on them.
What it knows that a grep does not
- The XML has the last word. The console can truncate, interleave, or count a retry
(
605/600is a real line from this repo).verdict_from_xmlreadsapp/build/outputs/androidTest-results/, and scopes to the newest run's own directory — AGP keepsconnected/andmanagedDevice/side by side and clears neither, so summing everything reported a 22-test run as 74. It always prints the results' age, because a verdict that is quietly ten minutes old is the same bug wearing a coat. - No results at all is not zero failures. A run that dies before any test reports writes no XML, and reading that as success is exactly how a red build gets called green.
- A stall is a result. No output for eight minutes gets reported, with a diagnosis, rather than looking like a slow test for another twenty.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 74 lines · 45 tokens per session scan A fb96bae6f1ed
watch-gradle-tests is a skill published in the GitHub repository parawanderer/OpenTagViewer (381 stars, last pushed 4d ago), licensed MIT. It adds 45 tokens to every session and 959 once invoked, about $0.0002 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.
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.
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running end-to-end UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.
argent-qa-flows
Create repeatable QA regression E2E tests as Argent flows from test cases, tickets, or acceptance criteria. Use when the user asks to generate or preserve an automated regression scenario, with deterministic setup, stable targets, executable structural or visual evidence, and two consecutive full passes. For one-off…
argent-create-flow
Create, record, edit, replay, or repair reusable Argent flow YAML files. Use when the user asks to record or replay a repeatable device path, set up profiling or an A/B comparison, or invoke the authoring engine behind argent-qa-flows. Also use before repeating three or more interactions. For one-off UI checks…