Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
apk-reverse — Agent skill for Android APK reverse engineering: dex patching, unpacking, repacking, ad and paywall removal, native .so analysis, and runtime instrumentation with Frida. | Kitploit
Tools/GitHubGitHub/newliver666/apk-reverse
Android SecurityStatic AnalysisDynamic Analysis (Sandboxing)Code AnalysisMobile App PentestingReverse EngineeringScripting & AutomationMalware AnalysisMobile SecurityBinary AnalysisLearning & Education
3.3k67711821 days agoReviewed by Kitploit

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share
GitHub
newliver666/apk-reverse

apk-reverse

Agent skill for Android APK reverse engineering: dex patching, unpacking, repacking, ad and paywall removal, native .so analysis, and runtime instrumentation with Frida.

View Repository

apk-reverse

English · 简体中文

stars forks license python android ci

Capabilities · Structure · Install · Requirements · Failure catalogue · Scope · Maintenance · Disclaimer

apk-reverse

An Agent Skill for Android APK reverse engineering, debloating, ad removal, surgical dex patching, repacking, and runtime/server analysis.

It is a skill, not a tutorial: it is written to be loaded by an agent (Claude Code, Codex, or any harness that supports the Agent Skills format) while it works, so it is organized for progressive disclosure — a short decision-oriented SKILL.md, detailed references loaded only when a step needs them, and parameterized scripts you can run directly.

How an agent is expected to consume this

SKILL.md is deliberately written as a procedure with gates rather than as advice, because the observed failure mode is not ignorance — it is a model reading the whole thing, agreeing with it, and then reasoning from first principles anyway.

So there are four things in the body that are meant to be acted on, not read:

  • Four override rules (R1–R4). Where they conflict with the current plan, they win until evidence overrides them.
  • A symptom index. Each row is a failure that has already been paid for. A matching row is a stop signal: load that file before running another command, rather than after a few more attempts. Reasoning past a known symptom is how the same hours get spent twice.
  • Four gates (G1–G4), each an action with a pass criterion. "I understand the idea" does not clear a gate. They exist so that classification, environment truth and a control build happen before the first patch, not after the third failure.
  • A two-strike rule and stop conditions. Two failures of the same shape mean the model is wrong, not the parameters. The third variant of a hypothesis that already failed twice is where rounds go to die.

And one thing at the end that is meant to be withheld: "done" has a definition (six items). A clean log is not one of them. Anything short of all six is a checkpoint, and should be reported as a checkpoint with what remains.

If you are an agent reading this: the cheapest possible first command is python skills/apk-reverse/scripts/doctor.py. It tells you which of these tools exist here, which scripts can actually run, and whether something in the environment is already poisoning your measurements.

What it is good at

Download Tool