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 noloman/Android-AI-skills --skill android-ci-cdgit clone --depth 1 https://github.com/noloman/Android-AI-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/noloman/android-ai-skills/android-ci-cd)<a href="https://agentmods.dev/skills/noloman/android-ai-skills/android-ci-cd"><img src="https://agentmods.dev/badge/skills/noloman/android-ai-skills/android-ci-cd/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/noloman/android-ai-skills/android-ci-cd"><img src="https://agentmods.dev/badge/skills/noloman/android-ai-skills/android-ci-cd.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00363 |
| Opus 5 | $0.00000 | $0.00181 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
android-ci-cd 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 9d 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.
What it actually says
name: android-ci-cd description: Android CI/CD — GitHub Actions, Fastlane, signing, Play Store deployment, build optimization. user-invocable: true
Android CI/CD
Cross-cutting skill — always activates alongside the project-type-specific skill.
Hard Rules
- Never store signing keys or passwords in the repository — use CI secrets.
- Run unit tests on every pull request — block merge on failure.
- Build release AAB in CI — not on developer machines.
- Upload mapping.txt and native symbols with every release build.
- Use Gradle build cache and configuration cache in CI.
- Pin all CI action versions to SHA hashes — not tags (supply chain security).
- Separate CI stages: lint → unit test → build → instrumented test → deploy.
- Never skip CI checks for hotfixes — no --no-verify equivalent.
- Cache Gradle dependencies and build outputs between runs.
- Use Gradle Managed Devices or Firebase Test Lab for instrumented tests in CI.
Core Patterns
- GitHub Actions with matrix strategy for testing on multiple API levels.
- Fastlane for automated screenshots, metadata management, and deployment.
- Decode signing keystore from base64 CI secret at build time.
- Use semantic-release or Gradle Play Publisher for automated releases.
- Run lint checks (detekt, ktlint, Android Lint) as CI gates.
- Separate pipelines: PR validation (fast) vs release (thorough).
- Use gradle/actions/setup-gradle instead of manual Gradle caching — handles cache, wrapper, and daemon automatically.
References
- references/github_actions.md
- references/fastlane.md
- references/signing_ci.md
- references/play_store_deployment.md
- references/build_optimization.md
What ships with it
5 files 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.
- 9d ago First seen · 39 lines · 0 tokens per session scan A 2e76855fec9f
android-ci-cd is a skill published in the GitHub repository noloman/Android-AI-skills (6 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 363 tokens. 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-31.
Other skills, from other repositories
eas-workflows
EAS service (paid). 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.
flutter-cicd
Set up CI/CD pipelines for Flutter apps. Use when configuring automated testing, build, or deployment workflows with GitHub Actions or Fastlane.
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.
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.
app-store-deployment
Publishes mobile applications to iOS App Store and Google Play with code signing, versioning, and CI/CD automation. Use when preparing app releases, configuring signing certificates, or setting up automated deployment pipelines.
swift-preflight
Audit a Swift / iOS / macOS repo for Xcode Cloud and TestFlight release blockers before upload - pbxproj drift, static build numbers, missing ciscripts, macOS App Store entitlements/Info.plist, headless-CI keychain tests, ad-hoc signing entitlement rejections, and flaky-UITest release gating. Reports PASS/WARN/FAIL…