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/and3r817/dot-claude-plugins/android-analysisnpx skills add and3r817/dot-claude-plugins --skill android-analysisgit clone --depth 1 https://github.com/and3r817/dot-claude-pluginsWrote 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/and3r817/dot-claude-plugins/android-analysis)<a href="https://agentmods.dev/skills/and3r817/dot-claude-plugins/android-analysis"><img src="https://agentmods.dev/badge/skills/and3r817/dot-claude-plugins/android-analysis.svg" alt="Measured on agentmods" 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 | $0.00063 | $0.04340 |
| Opus 5 | $0.00032 | $0.02170 |
| Sonnet 5 | $0.00013 | $0.00868 |
| Haiku 4.5 | $0.00006 | $0.00434 |
Grade B, and why
android-analysis scanned grade B with 1 finding 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 4d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
allowed-tools: Read, Grep, Glob, Bash(jadx:*), Bash(apktool:*), Bash(apkanalyzer:*), Bash(java:*), Bash(unzip:*), Bash(jar:*), Bash(tree:*), WebFetch, WebSearch How it starts
The opening of the file, as written. The whole thing — 535 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android & Java Binary Analysis
Purpose
Comprehensive reverse engineering toolkit combining JADX (Android DEX), CFR (Java JAR), apktool (Smali), and apkanalyzer (structure inspection) to decompile compiled binaries into readable source code. This skill provides systematic guidance for choosing the optimal tool for each reverse engineering scenario.
When to Use This Skill
Invoke this skill when:
- Decompiling APKs to Java source code for analysis
- Reverse engineering AAR/JAR libraries to understand implementations
- Extracting AndroidManifest.xml, resources, or assets from APKs
- Analyzing obfuscated or ProGuard/R8-protected code
- Understanding third-party SDK behavior or security practices
- Investigating app architecture, API integrations, or authentication flows
- Comparing different APK/library versions
- User explicitly mentions "decompile", "reverse engineer", "jadx", "apktool", or requests binary analysis
Core Concepts
Tool Selection Matrix
File Type Decision:
- APK → JADX (DEX to Java) or apktool (DEX to Smali)
- AAR → Extract classes.jar → CFR (best) or JADX (acceptable)
- JAR → CFR (primary) or Vineflower (modern Java 21+)
- DEX → JADX only
JADX (Android DEX Decompiler)
- Best for: APK and DEX files only
- Always use:
--deobfflag for obfuscated code - Use when: Analyzing Android apps, need GUI, or working with multi-format archives
- Limitation: Poor Java decompilation quality (fails Lambda/Stream operations)
CFR (Java JAR Decompiler)
- Best for: JAR files and extracted classes.jar from AAR
- Fastest speed (6.5s for 1.5MB JAR) with best readability
- Modern Java support (5-14) with excellent Lambda/Stream handling
- Use when: Analyzing Java libraries, need accurate decompilation, or JADX output is unreadable
Vineflower (Modern Java Decompiler)
- Best for: Java 21+ projects (records, sealed classes, pattern matching)
- Multithreaded decompilation with clean output formatting
- IntelliJ IDEA plugin available
- Use when: Working with cutting-edge Java features
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.
- 4d ago First seen · 535 lines · 63 tokens per session scan B 0b87ce701a75
android-analysis is a skill published in the GitHub repository and3r817/dot-claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 63 tokens to every session and 4,340 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
orchestrator
FULLY AUTONOMOUS Flutter development pipeline orchestrator. Smart routing: PM analyzes -> creates targeted tasks -> Orchestrator executes only needed agents. Supports Asana task URLs. Includes QE verification via Maestro E2E tests. 7-phase flow: PM -> TodoWrite -> Execute -> Review -> Tests -> QE E2E -> Close.
flutter-guide
Flutter/BLoC Clean Architecture patterns, review checklists, and testing guides. Background knowledge for flutter-dev, flutter-reviewer, flutter-tester. Not user-invocable.
maestro-flutter
Maestro E2E testing knowledge for Flutter apps. YAML-based flows, TestKeys, visual regression, Maestro MCP integration. Background knowledge for QE E2E testing phase.
enforcing-doc-hierarchy
Audit documentation against its declared hierarchy — broken links, duplicates, misplaced content, stale references, single-source-of-truth enforcement. Use for doc health reviews.
synthesizing-cc-bigpicture
Synthesizes a living big-picture meta-plan from Claude Code sessions, plans, tasks, and team communications. Use when orienting across projects, assessing reasoning modes, or creating a plan-to-plan overview.
distilling-plan-learnings
Extracts decisions, rejected alternatives, and patterns from recent plans into a persistent learnings document. Use after completing a plan or sprint.