Skip to content
Back to search

morphe-ai

MarketplaceWorks with Claude CodeGitHub

Claude Code plugins and skills for authorized Morphe Android patch development.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked yesterday
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/paresh-maheshwari--morphe-ai/badge.svg)](/listings/paresh-maheshwari--morphe-ai)

HTML

<a href="/listings/paresh-maheshwari--morphe-ai"><img src="/api/listings/paresh-maheshwari--morphe-ai/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Inside Claude Code, add this repository as a marketplace and install the plugin by name:

/plugin marketplace add Paresh-Maheshwari/morphe-ai
/plugin install morphe-patch-creator@morphe-ai

Equivalent shell commands, with an explicit scope:

claude plugin marketplace add Paresh-Maheshwari/morphe-ai --scope user
claude plugin install morphe-patch-creator@morphe-ai --scope user

Use `--scope project` to share enablement through a repository, or `--scope local` for an uncommitted project-local install. Update or remove later with:

claude plugin update morphe-patch-creator@morphe-ai      # restart Claude Code to apply
claude plugin uninstall morphe-patch-creator@morphe-ai   # add --keep-data to preserve plugin data

Cloning this repository alone does **not** register or install the plugin — you add the marketplace and install by name as above.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 24 lines
  1. {
  2. "name": "morphe-ai",
  3. "description": "Claude Code plugins and skills for authorized Morphe Android patch development.",
  4. "owner": {
  5. "name": "Paresh Maheshwari",
  6. "email": "Paresh-Maheshwari@users.noreply.github.com"
  7. },
  8. "plugins": [
  9. {
  10. "name": "morphe-patch-creator",
  11. "displayName": "Morphe Patch Creator",
  12. "source": "./plugins/morphe-patch-creator",
  13. "description": "Claude-first workflow for authorized Android APK analysis and Morphe patch development.",
  14. "version": "0.1.0",
  15. "author": {
  16. "name": "Paresh Maheshwari"
  17. },
  18. "homepage": "https://github.com/Paresh-Maheshwari/morphe-ai",
  19. "repository": "https://github.com/Paresh-Maheshwari/morphe-ai",
  20. "license": "GPL-3.0-only",
  21. "keywords": ["android", "apk", "morphe", "patching"]
  22. }
  23. ]
  24. }
README.md · README · 418 lines
  1. # Morphe AI
  2. AI-powered Android APK patching workspace. Multi-agent pipeline that automates: APK analysis → decompilation → target hunting → patch writing → build & deploy.
  3. Built with [Kiro CLI](https://kiro.dev), but the prompts, skills, and steering context are **model-agnostic** — adapt them to any AI coding assistant (Cursor, Copilot, Cline, Aider, Claude Code, etc.).
  4. **Author:** [Paresh Maheshwari](https://github.com/Paresh-Maheshwari)
  5. **Repository:** [morphe-ai](https://github.com/Paresh-Maheshwari/morphe-ai)
  6. ## Claude Code Plugin
  7. This repository is a Claude Code plugin marketplace. It ships the **Morphe Patch Creator** plugin
  8. under `plugins/morphe-patch-creator/`, defined by the marketplace manifest at
  9. `.claude-plugin/marketplace.json`.
  10. ### Install from GitHub (anyone)
  11. Inside Claude Code, add this repository as a marketplace and install the plugin by name:
  12. ```text
  13. /plugin marketplace add Paresh-Maheshwari/morphe-ai
  14. /plugin install morphe-patch-creator@morphe-ai
  15. ```
  16. Equivalent shell commands, with an explicit scope:
  17. ```bash
  18. claude plugin marketplace add Paresh-Maheshwari/morphe-ai --scope user
  19. claude plugin install morphe-patch-creator@morphe-ai --scope user
  20. ```
  21. Use `--scope project` to share enablement through a repository, or `--scope local` for an
  22. uncommitted project-local install. Update or remove later with:
  23. ```bash
  24. claude plugin update morphe-patch-creator@morphe-ai # restart Claude Code to apply
  25. claude plugin uninstall morphe-patch-creator@morphe-ai # add --keep-data to preserve plugin data
  26. ```
  27. Cloning this repository alone does **not** register or install the plugin — you add the
  28. marketplace and install by name as above.
  29. ### Load from a local checkout (development)
  30. ```bash
  31. claude --plugin-dir ./plugins/morphe-patch-creator
  32. ```
  33. Validate before loading when developing:
  34. ```bash
  35. claude plugin validate --strict ./plugins/morphe-patch-creator
  36. claude plugin validate --strict .
  37. ```
  38. ### Start the pipeline
  39. ```text
  40. /morphe-patch-creator:create-patch ./path/to/app.apk "describe the authorized change"
  41. ```
  42. The primary skill delegates to focused recon, decompiler, target-hunter, patch-writer, and validator subagents. Device testing and Git/GitHub submission remain explicit-only commands. See [`plugins/morphe-patch-creator/README.md`](plugins/morphe-patch-creator/README.md) for configuration, dependencies, install scopes, and safety boundaries.
  43. > **Not sure how to use it? Just ask.** Both Kiro and Claude already carry this repo's skills and
  44. > steering context, so you don't need to memorize commands. Say something like *"how do I create a
  45. > patch?"* or *"what do you need from me to patch this APK?"* and the agent explains the workflow
  46. > and walks you through the next step.
  47. ## Using with Other AI Models
  48. The real value is in `.kiro/steering/` and `.kiro/prompts/` — portable markdown files you can use with any AI tool:
  49. | Directory | Content |
  50. |-----------|---------|
  51. | `steering/core/` | Project overview, workspace layout |
  52. | `steering/patching/` | Patch writing guides, APIs, extension development |
  53. | `steering/bytecode/` | Smali cheat sheet, fingerprinting, obfuscation guide |
  54. | `steering/patterns/` | Billing bypass, ad blocking, protection bypass patterns |
  55. | `steering/community/` | Patterns learned from 10+ community patch repos |
  56. | `steering/build/` | Build commands, CLI reference, troubleshooting |
  57. | `prompts/` | Agent role prompts (recon, decompiler, hunter, writer, deployer) |
  58. | `skills/` | On-demand knowledge (tool reference, FAQ, examples) |
  59. **To use with your AI tool:**
  60. 1. Feed the relevant steering `.md` files as context/rules
  61. 2. Use the prompts as system instructions
  62. 3. Adapt the agent configs to your tool's format (e.g., `.cursorrules`, `.github/copilot-instructions.md`)
  63. ## Prerequisites
  64. - **Kiro CLI** installed and configured
  65. - **JDK 21** recommended (aligns with template CI); JDK 17 is the minimum stated in desktop source
  66. - **JRE 21+** required to run the CLI
  67. - **Android RE tools:**
  68. | Tool | Purpose | Install |
  69. |------|---------|---------|
  70. | jadx | Decompile APK → Java source | `sudo apt install jadx` |
  71. | baksmali | Disassemble DEX → smali (local analysis only) | `sudo apt install libsmali-java` |
  72. | apktool | Decode/rebuild APK resources | `sudo apt install apktool` |
  73. | aapt | Read APK manifest/metadata | `sudo apt install aapt` |
  74. | ripgrep (rg) | Fast regex search | `sudo apt install ripgrep` |
  75. | adb | Install APKs on device | `sudo apt install adb` |
  76. | dex2jar | Convert DEX → JAR | `sudo apt install dex2jar` |
  77. | apkid | Detect obfuscators/packers | `uvx apkid` (no install needed) |
  78. | kaggle | Remote decompilation API | `pip install kaggle` |
  79. > **Note:** `baksmali` from apt is used only for local DEX analysis and manual smali reading.
  80. > Patch builds use the Gradle plugin's own pinned baksmali/smali fork automatically.
  81. Quick install all:
  82. ```bash
  83. sudo apt install -y openjdk-21-jdk jadx libsmali-java apktool aapt ripgrep adb dex2jar
  84. pip install kaggle
  85. ```
  86. ## Quick Setup
  87. ```bash
  88. # 1. Clone
  89. git clone https://github.com/Paresh-Maheshwari/morphe-ai.git morphe && cd morphe
  90. # 2. Create .env with your secrets
  91. cp .env.example .env
  92. # Edit .env — add your KAGGLE_API_TOKEN
  93. # 3. Gradle auth (for morphe patcher dependencies)
  94. mkdir -p ~/.gradle
  95. cat >> ~/.gradle/gradle.properties << EOF
  96. gpr.user = <your-github-username>
  97. gpr.key = <github-pat-with-read:packages>
  98. EOF
  99. # 4. Clone your patches repo
  100. # You can use any folder name — set MORPHE_PATCHES_DIR to match (default: morphe-patches)
  101. export MORPHE_PATCHES_DIR=morphe-patches # or any name you prefer
  102. git clone <your-patches-repo> "${MORPHE_PATCHES_DIR}"
  103. # 5. Setup CLI (downloads latest from GitHub)
  104. ./setup-cli.sh
  105. # 6. Start Kiro (this CLI is `kiro-cli`; `kiro` also works if aliased)
  106. kiro-cli chat
  107. ```
  108. ## Environment Variables
  109. | Variable | Required | Description |
  110. |----------|----------|-------------|
  111. | `MORPHE_PATCHES_DIR` | No | Path to your patches repo clone. Default: `morphe-patches` |
  112. | `KAGGLE_API_TOKEN` | Yes | From https://kaggle.com/settings → API → Create New Token |
  113. | `KAGGLE_KERNEL_ID` | Yes | Your Kaggle username + notebook name (e.g. `myuser/jadx-apk-decompiler`) |
  114. | `GITHUB_TOKEN` | Yes (for gradle) | GitHub → Settings → Developer → PAT with `read:packages` |
  115. | `MORPHE_DATA_DIR` | No | Override CLI data root (default: `morphe-data/` beside the real jar, then home/XDG fallback). Contains downloaded `patches/`, logs, tmp, and `morphe.keystore` |
  116. ### Configuring a custom patches directory
  117. All agent commands resolve the patches repo via `MORPHE_PATCHES_DIR`. Set it once in your shell profile or `.env` file:
  118. ```bash
  119. export MORPHE_PATCHES_DIR=my-custom-patches # folder name, relative to workspace root
  120. ```
  121. The agents and prompts use `${MORPHE_PATCHES_DIR:-morphe-patches}` so they fall back to `morphe-patches` if the variable is unset — no manual editing of every agent file required.
  122. Kiro agent filesystem allowlists use scoped `**/patches/**` and `**/extensions/**` globs because static JSON resource paths cannot interpolate `MORPHE_PATCHES_DIR`; prompts still resolve and write only within the configured patch repository.
  123. ## Kaggle Setup (Remote Decompilation)
  124. The `jadx-decompile` script runs decompilation on Kaggle's free servers (4 cores, 28GB RAM) because jadx needs a lot of memory for large APKs.
  125. ### How it works
  126. 1. You provide a **direct download URL** of the APK (not a webpage link)
  127. 2. Script generates a Kaggle notebook that downloads the APK and runs jadx
  128. 3. Pushes notebook to Kaggle, waits for completion
  129. 4. Downloads the decompiled output (zip) to your local machine
  130. ### What it needs
  131. - A **direct APK download link** — the URL must directly download the file when opened
  132. - ✅ `https://download.apkmirror.com/wp-content/themes/APKMirror/download.php?id=12345`
  133. - ❌ `https://www.apkmirror.com/apk/com.example/app-name/` (this is a page, not a download)
  134. - APKMirror download links expire after ~1 hour — use fresh links
  135. ### Setup steps
  136. 1. Create a free Kaggle account: https://kaggle.com
  137. 2. Go to Settings → API → Create New Token (gives you `KGAT_...` token)
  138. 3. Create a **private** notebook: https://kaggle.com/notebooks → New Notebook
  139. - Name it exactly: `jadx-apk-decompiler`
  140. - Set to **private**
  141. - Enable **internet access** in notebook settings
  142. 4. Add to your `.env`:
  143. ```
  144. KAGGLE_API_TOKEN=KGAT_your_token_here
  145. KAGGLE_KERNEL_ID=your-kaggle-username/jadx-apk-decompiler
  146. ```
  147. ### Usage
  148. ```bash
  149. .kiro/jadx-decompile "https://direct-download-url" analysis/<app>/
  150. ```
  151. ## Workspace Structure
  152. ```
  153. morphe/
  154. ├── .env.example # Template for secrets
  155. ├── .gitignore # Ignores secrets, binaries, large folders
  156. ├── AGENTS.md # Main orchestrator prompt
  157. ├── LICENSE # GPL-3.0 license
  158. ├── README.md # This file
  159. ├── setup-cli.sh # CLI download script
  160. └── .kiro/
  161. ├── agents/ # 6 agent configs
  162. ├── prompts/ # Agent prompt files
  163. ├── skills/ # 13 on-demand skills
  164. ├── steering/ # 32 always-loaded context files
  165. │ ├── core/ # Project overview (morphe agent)
  166. │ ├── build/ # Build/CLI reference (patch-deployer)
  167. │ ├── patching/ # Patch writing guides (patch-writer)
  168. │ ├── bytecode/ # Smali/fingerprinting (patch-writer + target-hunter)
  169. │ ├── patterns/ # Bypass patterns (target-hunter)
  170. │ └── community/ # Community patch analysis (target-hunter)
  171. ├── settings/ # LSP config
  172. └── jadx-decompile # Remote decompiler script
  173. # Created locally after setup (gitignored):
  174. ├── .env # Your secrets
  175. ├── morphe-cli.jar # CLI binary (created by setup-cli.sh)
  176. ├── morphe-data/ # CLI data root (downloaded patches, logs, tmp, morphe.keystore)
  177. ├── morphe-patches/ # Your patches repo clone (name set by MORPHE_PATCHES_DIR)
  178. └── analysis/ # APK analysis work (per-app folders)
  179. └── <app>/
  180. ├── apk/ # Original APK files (created by apk-recon)
  181. ├── notes/ # Analysis findings (created by apk-recon)
  182. ├── decompiled/ # Java source from jadx (created by apk-decompiler)
  183. ├── smali/ # Bytecode from baksmali (created by apk-decompiler)
  184. └── builds/ # Patched APKs (created by patch-deployer)
  185. ```
  186. ## Agents
  187. ### morphe (orchestrator)
  188. - **Trigger:** Default agent — always active
  189. - **What it does:** Checks pipeline state for any app and routes you to the correct specialist
  190. - **Tools:** All (bash, grep, glob, code, web search, knowledge)
  191. - **Context:** Core project overview
  192. - **Handles directly:** Quick builds, status checks, code searches, file reads
  193. ### apk-recon
  194. - **Trigger:** "Recon this APK" or give it a file path
  195. - **What it does:** Identifies APK metadata — package name, version, protections, framework, APK type
  196. - **Tools:** aapt, apkid, unzip, file
  197. - **Input:** APK file path in project root
  198. - **Output:** `analysis/<app>/notes/recon.md` + organized `apk/` folder
  199. - **Context:** APK analysis skill, apktool skill
  200. ### apk-decompiler
  201. - **Trigger:** "Decompile `<app>` — URL is `<url>`"
  202. - **What it does:** Decompiles to Java and extracts smali from all DEX files. Kaggle (28GB RAM) is the primary path — explains the data flow and gets your approval before uploading; local jadx is the fallback for small APKs or when you decline remote
  203. - **Tools:** jadx-decompile script, baksmali, unzip
  204. - **Input:** App name + direct APK download URL
  205. - **Output:** `analysis/<app>/decompiled/` (Java) + `analysis/<app>/smali/` (bytecode)
  206. - **Context:** APK analysis skill, jadx skill, tool reference
  207. ### target-hunter
  208. - **Trigger:** "Find targets for `<app>` — looking for `<premium/ads/gates>`"
  209. - **What it does:** Searches decompiled code for billing SDKs, ads, feature gates. Verifies every finding against smali bytecode. Documents fingerprint strategies.
  210. - **Tools:** rg (ripgrep), glob, code (LSP), thinking
  211. - **Input:** App name + what to find
  212. - **Output:** `analysis/<app>/notes/premium-bypass.md`, `ad-removal.md`, etc.
  213. - **Context:** Billing/ad/protection bypass patterns, community patch analysis, smali/fingerprinting guides
  214. ### patch-writer
  215. - **Trigger:** "Write patches for `<app>`"
  216. - **What it does:** Reads target findings, cross-checks against smali, writes Kotlin fingerprints + patch code, builds and verifies
  217. - **Tools:** rg, glob, code (LSP), gradle, thinking
  218. - **Input:** App name (reads notes automatically)
  219. - **Output:** `.kt` files in `${MORPHE_PATCHES_DIR:-morphe-patches}/patches/src/...`
  220. - **Context:** Patch development guides, patcher APIs, bytecode utilities, real patch examples, advanced techniques
  221. ### patch-deployer
  222. - **Trigger:** "Build and test `<app>`"
  223. - **What it does:** Builds patches with gradle, patches APK with morphe-cli, installs via ADB, reports results
  224. - **Tools:** gradle, morphe-cli, adb, git
  225. - **Input:** App name + action (build/test/deploy)
  226. - **Output:** `analysis/<app>/builds/<app>_patched.apk`
  227. - **Context:** Build/CLI reference, troubleshooting guide
  228. ## Pipeline
  229. ```
  230. 1. RECON → apk-recon identifies the APK
  231. 2. DECOMPILE → apk-decompiler runs jadx + baksmali
  232. 3. HUNT → target-hunter finds patchable targets
  233. 4. WRITE → patch-writer creates Kotlin patches
  234. 5. BUILD+DEPLOY → patch-deployer builds, patches APK, installs
  235. ```
  236. Just give the morphe agent an app name — it checks state and tells you which agent to switch to next.
  237. ## Usage Examples
  238. ```
  239. # Start fresh with a new APK
  240. > I have a new APK for truecaller
  241. # Continue work on existing app
  242. > truecaller
  243. # Quick tasks (morphe handles directly)
  244. > build patches
  245. > list patches
  246. > search for "isPremium" in truecaller
  247. > what's the status of all apps?
  248. ```
  249. ## Customization
  250. ### Adding a new app
  251. 1. Download APK to project root
  252. 2. Tell morphe agent: "New APK for `<app>`"
  253. 3. Follow the pipeline
  254. ### Modifying agent behavior
  255. - Edit prompts in `.kiro/prompts/`
  256. - Edit configs in `.kiro/agents/`
  257. - Add steering files to `.kiro/steering/<category>/`
  258. ### Adding new steering context
  259. Place `.md` files in the appropriate category folder. They auto-load for agents that reference that folder.
  260. ### Updating the jadx-decompile script
  261. If you change your Kaggle username, update `KAGGLE_KERNEL_ID` in your `.env` file.
  262. ## Signing Key
  263. The CLI uses `morphe-data/morphe.keystore` by default. It reuses that key across desktop runs,
  264. so desktop-patched APKs can update each other. It is not automatically the same key held by
  265. Morphe Manager on a phone; export/import the key or pass the same custom `--keystore` when both
  266. environments must share a signing identity. No project-root keystore file is required.
  267. ### Export from Morphe Manager (recommended, to match existing key)
  268. 1. Open Morphe Manager on your phone
  269. 2. Go to Settings → Export keystore
  270. 3. Transfer the exported `.keystore` file to your project
  271. 4. Pass it via `--keystore <path>` when patching
  272. ### Generate new keystore (if starting fresh without Morphe Manager)
  273. ```bash
  274. keytool -genkey -v -keystore my.keystore -alias Morphe \
  275. -keyalg RSA -keysize 2048 -validity 10000 \
  276. -storepass morphe -keypass morphe
  277. ```
  278. Then import into Morphe Manager: Settings → Import keystore.
  279. ### Usage with custom keystore
  280. ```bash
  281. java -jar morphe-cli.jar patch -p patches.mpp --keystore my.keystore -o out.apk input.apk
  282. ```
  283. ## Troubleshooting
  284. | Issue | Fix |
  285. |-------|-----|
  286. | Gradle auth fails | Check `~/.gradle/gradle.properties` has `gpr.user` + `gpr.key` |
  287. | jadx-decompile fails | Check `.env` has `KAGGLE_API_TOKEN`, verify with `kaggle kernels list` |
  288. | Fingerprint doesn't match | App version changed — re-run target-hunter to verify smali |
  289. | Build fails | Check error in patch-deployer output — it gives exact file + line |
  290. | ADB not found | `sudo apt install adb` or connect device |
  291. | Agent gives wrong answer | Check steering files are loading: `/context show` in Kiro |
  292. | CLI fails to start | Ensure JRE 21+ is installed and `JAVA_HOME` is set correctly |
  293. ## Community Patch Repos (Reference)
  294. The steering files in `.kiro/steering/community/` contain patterns learned from these repos:
  295. | Repo | Focus | Patterns |
  296. |------|-------|----------|
  297. | [morphe-patches (hoo-dles)](https://github.com/hoo-dles/morphe-patches) | Various apps | Method injection, signature spoof, extension-based ad skip |
  298. | [De-ReVanced](https://github.com/RookieEnough/De-ReVanced) | YouTube/Music | Device ID spoofing, signature bypass |
  299. | [revanced-patches (anddea)](https://github.com/anddea/revanced-patches) | Extended YouTube | Advanced ad blocking, SponsorBlock |
  300. | [piko](https://github.com/crimera/piko) | Instagram | Entity patterns, JSON field replacement, feed filtering |
  301. | [patcheddit](https://github.com/wchill/patcheddit) | Reddit | Client ID spoofing, OAuth override, matchAll() bulk replace |
  302. | [adobo](https://github.com/jkennethcarino/adobo) | Universal ad blocking | Per-SDK ad removal (AdMob, Unity, AppLovin, IronSource) |
  303. | [AmpleReVanced](https://github.com/AmpleReVanced/revanced-patches) | Spotify | Hex patching native libs, protocol spoofing |
  304. | [morphe-meta-patches](https://github.com/MeridianFresco/morphe-meta-patches) | Facebook/Meta | Sponsored content removal, story filtering |
  305. | [binarymend](https://github.com/binarymend/morphe-patches) | Various apps | Telemetry blocking, bulk analytics disable |
  306. ## Contributing
  307. **PRs welcome!** This project benefits from community knowledge. You can help by:
  308. - 🧠 **Improving prompts** — better instructions, fewer hallucinations, more accurate patches
  309. - 📚 **Adding steering context** — document new bypass patterns, SDK techniques, or app architectures
  310. - 🛠️ **Adding skills** — new on-demand knowledge files for specific tools or workflows
  311. - 🤖 **Adapting to other AI tools** — configs for Cursor, Copilot, Cline, Aider, etc.
  312. - 📝 **Documenting patterns** — analyzed a new app? Share the technique
  313. - 🐛 **Fixing issues** — found a wrong instruction or bad fingerprint pattern? Fix it
  314. ### How to contribute
  315. 1. Fork this repo
  316. 2. Create a branch: `git checkout -b feat/your-improvement`
  317. 3. Make your changes (add/edit files in `.kiro/steering/`, `.kiro/prompts/`, `.kiro/skills/`)
  318. 4. Open a PR with a clear description of what you improved
  319. ### Contribution ideas
  320. - Add patterns for new billing SDKs (Adapty, Qonversion, Glassfy)
  321. - Add patterns for new ad SDKs (InMobi, IronSource, Chartboost)
  322. - Improve fingerprint debugging guidance
  323. - Add support files for other AI tools (`.cursorrules`, `.github/copilot-instructions.md`)
  324. - Document Flutter/React Native patching techniques
  325. - Add more real-world patch examples
  326. ## License
  327. GPL-3.0-only. See [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.