android-reverse-engineering

A toolkit for examining Android APK, JAR, and AAR files by turning compiled code back into readable source-like code. APK is an Android app package; JAR and AAR are Java and Android library packages.

In plain words
What is it for?
Decompiling packages with jadx, tracing how calls move through libraries, and documenting the APIs that can be extracted.
Why use it?
It helps developers understand how an Android app or library works when the original source code is unavailable or difficult to follow.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add CreditTone/android-reverse-engineering-skill
agentmods
npx agentmods add plugins/credittone/android-reverse-engineering-skill/android-reverse-engineering
Clone the repo
git clone --depth 1 https://github.com/CreditTone/android-reverse-engineering-skill

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Security

Grade A, and why

android-reverse-engineering 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 yesterday.

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.

Origin

This is a copy

100% identical to android-reverse-engineering — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

android-reverse-engineering/.claude-plugin/plugin.json · 14 lines

What it actually says

{
  "name": "android-reverse-engineering",
  "version": "1.0.0",
  "description": "Decompile Android APK/JAR/AAR with jadx, trace call flows through libraries, and document extracted APIs.",
  "author": {
    "name": "Simone Avogadro"
  },
  "repository": "https://github.com/SimoneAvogadro/android-reverse-engineering-skill",
  "license": "Apache-2.0",
  "keywords": ["android", "reverse-engineering", "apk", "jadx", "decompile", "api-extraction"],
  "skills": "./skills/",
  "commands": "./commands/"
}
Changes

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.

  1. yesterday First seen · 14 lines scan A 613e33718c8c

Subscribe to this mod's changes

android-reverse-engineering is a plugin published in the GitHub repository CreditTone/android-reverse-engineering-skill (435 stars, last pushed 3mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 100% identical to android-reverse-engineering, differing in 2 lines, and is treated as a copy.