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 scripting-adb-for-cigit 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/scripting-adb-for-ci)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/scripting-adb-for-ci"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/scripting-adb-for-ci/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/scripting-adb-for-ci"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/scripting-adb-for-ci.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.00270 | $0.06919 |
| Opus 5.5 | $0.00108 | $0.02768 |
| Sonnet 5.5 | $0.00054 | $0.01384 |
| Haiku 4.5 | $0.00027 | $0.00692 |
Grade A, and why
scripting-adb-for-ci 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scripting adb For CI — Bash Idioms, Exit Codes, Fan-out
This skill is the connective tissue that turns the other ADB skills into a CI pipeline: exit-code propagation, retries, timeouts, parallel device fan-out, port forwarding, idempotent setup, capture-on-failure, and Test Orchestrator wiring. Each section cross-links to the skill that owns the underlying primitive.
When to use this skill
- A CI job invokes
adb shell am instrumentand "passes" even when tests fail — it gates on$?, butam instrumentalways exits0; the real status lives inINSTRUMENTATION_STATUS_CODElines on stdout (and-wis needed just to get that stdout at all). - The team has multiple physical devices on a single agent and wants to run sharded tests in parallel.
adb forwardandadb reverseare confused — most teams have at least one bug from the opposite argument order.- Transient
error: device not found/error: closedfailures are not retried; the job fails on the first hiccup. - A script lacks cleanup so leaked port forwards or modified
settings put global ...survive into the next run. - The team wires Test Orchestrator with
androidTestImplementation— the build silently fails to install the orchestrator APK.
When NOT to use this skill
- The single primitive (logcat, screencap, pull, push, settings, input, am instrument) is not yet understood. Read the relevant sibling skill first.
- The CI itself (Gradle plugin, Firebase Test Lab cloud config). Use FTL's own docs for that layer.
- Compose / instrumentation test mechanics. Use
../../../compose/synchronization/synchronizing-with-idle/SKILL.mdand friends.
Prerequisites
- Bash (zsh works for most of this; macOS users should
brew install coreutilsforgtimeoutif relying ontimeout). - Platform Tools 24+ on the host. On older toolchains
adb shellexit codes are unreliable. - Devices on API 24+ for reliable shell exit-code propagation. Pre-Nougat use a sentinel
__ADB_RC=$?in stdout and grep on the host.
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 · 500 lines · 270 tokens per session scan A 1a1194eb2446
scripting-adb-for-ci is a skill published in the GitHub repository skydoves/android-testing-skills (337 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 270 tokens to every session and 6,919 once invoked, about $0.0011 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
eas-workflows
Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI/CD or workflows in an Expo or EAS context, mentions .eas/workflows/, or wants help with EAS build pipelines or deployment automation.
mobiai-community-android-github-actions
Use when creating, updating, or reviewing reusable GitHub Actions workflows for Android unit tests or instrumented tests, especially when the workflow should ask about triggers, caching, emulator setup, and action-version checks.
github-actions
GitHub Actions workflow patterns for React Native iOS simulator and Android emulator cloud builds with downloadable artifacts. Use when setting up CI build pipelines or downloading GitHub Actions artifacts via gh CLI and GitHub API.
flutter-cicd
Set up CI/CD pipelines for Flutter apps. Use when configuring automated testing, build, or deployment workflows with GitHub Actions or Fastlane.
android-tooling
Configure Android static analysis with Detekt, Ktlint, and Android Lint for CI/CD quality gates. Use for Android-specific lint and quality tooling; defer generic Java Checkstyle, SonarQube, and standalone CI configuration.
agent-mobile-release-manager
Specialist subagent: App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta…