Install
$ agentstack add skill-josephsanjaya-skills-android-leak-expert ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Android Leak Expert
Identify, profile, and fix memory leaks in Android applications (Java, Kotlin, Jetpack Compose, JNI).
Symmetrically unbind resources in lifecycles, collect flow streams lifecycle-aware, use static classes with WeakReference for background work, and manually clear native/JNI references.
1. Quick Decision Tree
- Suspicious code scan → Run scan script (
scripts/scan_leak_vectors.py) - Profile memory / investigate heap dump → Heap Profiling & Dominator Trees ([references/debuggingandsolutions.md#2-heap-diagnostics--profiling](references/debuggingandsolutions.md#2-heap-diagnostics--profiling))
- Fix classic view/fragment leak → Teardown & Lifecycle Binding ([references/debuggingandsolutions.md#3-classic-leak-patterns--solutions](references/debuggingandsolutions.md#3-classic-leak-patterns--solutions))
- Fix Compose/flow state leak → Compose Flow Collection & Effect Cleanups ([references/jetpackcompose.md](references/jetpackcompose.md))
- Fix native C++/JNI leak → Native JNI Frame & Registry Release ([references/debuggingandsolutions.md#4-jni-native-memory-management](references/debuggingandsolutions.md#4-jni-native-memory-management))
- Set up CI/CD verification → Trap-Tests & JUnit RuleChains ([references/debuggingandsolutions.md#5-enterprise-scale-observations](references/debuggingandsolutions.md#5-enterprise-scale-observations))
- Now In Android reference → View code patterns ([references/nowinandroid.md](references/nowinandroid.md))
2. Fast Command Tools
Scan target code directory for common memory leaks:
python3 scripts/scan_leak_vectors.py
3. Clean Code Reference Implementations
- Safe Handler Pattern: [SecureHandlerSample.kt](assets/SecureHandlerSample.kt)
- Safe Fragment Adapter Binding: [SecureFragmentSample.kt](assets/SecureFragmentSample.kt)
- Safe Compose Lifecycle: [SecureComposeLifecycleSample.kt](assets/SecureComposeLifecycleSample.kt)
Developers must follow these rules. Ensure all custom handlers are static, fragments should nullify bindings/adapters in onDestroyView, and compose collections must only use collectAsStateWithLifecycle.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: JosephSanjaya
- Source: JosephSanjaya/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.