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 agentmods add skills/nevaberry/nevaberry-plugins/android-sdk-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill android-sdk-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWhat 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 | $0.00009 | $0.02264 |
| Opus 5 | $0.00005 | $0.01132 |
| Sonnet 5 | $0.00002 | $0.00453 |
| Haiku 4.5 | $0.00001 | $0.00226 |
Grade A, and why
android-sdk-knowledge-patch 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 2d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android SDK Knowledge Patch
Use this skill when updating Android applications, libraries, build logic, or
Play delivery settings where recent platform and Android Gradle Plugin behavior
can affect compatibility. Check the project's compileSdk, targetSdk,
minSdk, AGP, Gradle, JDK, Kotlin, KSP, NDK, and form factors before applying
target-gated guidance.
Prefer the project's manifests, build files, tests, and observed runtime
behavior when they differ from general guidance. Distinguish changes affecting
all apps on a platform release from changes gated by targetSdk.
Reference index
| Reference | Topics |
|---|---|
| AGP toolchain and APIs | Toolchain floors, Kotlin, public DSL, Variant API, removed APIs, migration staging |
| Bluetooth, media, and devices | Bluetooth, companions, health, camera, codecs, alarms, widgets, device integration |
| Google Play target API policy | Submission floors, existing-app availability, extensions, exemptions |
| R8, packaging, and testing | Shrinking, keep rules, packaging, native compatibility, reports, profiling |
| Runtime, UI, and scheduling | Jobs, concurrency, back, edge-to-edge, large screens, IME, audio, desktop UI |
| Security, networking, and data | Intents, LAN access, TLS, SMS, contacts, URI grants, Keystore, media access |
Start with the compatibility gates
- Read
compileSdk,targetSdk,minSdk, AGP, Gradle, and JDK from the project rather than assuming they move together. - Identify device and form-factor scope: phone, tablet, desktop windowing, Wear OS, Android Auto, Automotive OS, TV, or XR.
- Separate platform-wide behavior from target-gated behavior in tests.
- Exercise compatibility flags only as temporary diagnostics; implement the durable behavior before raising the target SDK.
- For build plugins, migrate to lazy public APIs before enabling stricter AGP behavior.
What ships with it
7 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.
- 2d ago First seen · 231 lines · 9 tokens per session scan A d9b3ebf3f114
android-sdk-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 6d ago), licensed MIT. It adds 9 tokens to every session and 2,264 once invoked, about $0.0000 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
swiftui-pro
Use when writing, reviewing, or refactoring SwiftUI code — covers modern state management (@Observable), NavigationStack, layout, performance, and accessibility for iOS 26 / Swift 6.
swift-architecture-pro
Use when structuring an iOS app — feature modularization, MVVM with @Observable, dependency injection, navigation routing, and layering for testability.
android-kotlin-compose
Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…
android-kotlin-coroutines
Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…
android
Generate Android/Kotlin project with Jetpack.
canvas
Display HTML content on connected OpenClaw nodes (Mac app, iOS, Android).