Which tool, Agent?
APK, ELF, JS, PCAP — your agent doesn't know whether to reach for jadx, Frida, IDA, or BurpSuite. So it guesses commands and burns your time.
v1.1.0 · MIT licensed · active development · for authorized work
reverse-skill is a skills router for AI coding agents. When your agent hits an APK, a binary, encrypted frontend JS, a CTF challenge, or an authorized pentest target, it routes to the right methodology — gates it on authorization, boots missing tools, and leaves an evidence-backed report.
“Navigate the dark waters, sail against the stream.”
English-first rebuild of the MIT-licensed upstream reverse-skill project.
Live GitHub data · TT88990/reverse-skill-english · refreshed every 10 minutes
// 01 · star growth
GitHub now restricts public star-history data, so this site shows the live star count instead of a historical chart.
GitHub Stars
TT88990/reverse-skill-englishStars on TT88990/reverse-skill-english, fetched live from the GitHub API.
Star history is currently unavailable due to GitHub API restrictions
// 02 · the problem
Four failures repeat in every AI-assisted reverse engineering or pentest session.
APK, ELF, JS, PCAP — your agent doesn't know whether to reach for jadx, Frida, IDA, or BurpSuite. So it guesses commands and burns your time.
Every task type needs a different methodology. APK, binary, frontend JS, and CTF playbooks are spread across docs, folders, and half-remembered chat history.
“Works on my machine.” Tools, MCP servers, and scripts live on different machines. Change environments and the whole setup silently stops working.
The same mistakes get made again and again. Each session starts from zero, and everything learned dies when the conversation ends.
// 03 · the workflow
The same repeatable chain runs on Windows, Linux, and macOS — regardless of which AI client you use.
Describe the job in plain language: an APK, some encrypted JS, a CTF challenge, an authorized target.
RULES.md applies the global routing rules first — the authorization gate that runs before any action.
master-route.ps1 scores the hint against 41 priority rules (R0–R40) and prints the PRIMARY path with a one-line reason.
case-init writes scope.md with auth.status=granted and a network profile. No target action before this — the guard exits 2.
The PRIMARY skill opens: apk-reverse, js-reverse, pwn-chain, or one of 40+ modules, each with its ACTION REQUIRED checklist.
Tool paths come from tool-index.md only. Missing tools bootstrap on demand from pinned, hash-checked manifests.
timeline → Evidence → Finding → Path. Reports land in report/, sanitized lessons in field-journal.
// 04 · core features
The package is deliberately small: routing, bootstrapping, and learning. Everything else is a playbook on top.
41 priority rules · R0–R40 · client-neutral
Semantics beat tool names. The router scores your task against structured keyword rules and picks the PRIMARY path with a documented reason. No match? R0 catches it.
tool-index · pinned manifests
A local index records what is actually installed on this machine. Missing capabilities install on demand from pinned, hash-checked manifests — never from guesswork.
field-journal · evidence chain
Every case keeps a timeline, evidence IDs, findings, and a review pass. De-identified lessons are written back to field-journal, so the same hole doesn't catch you twice.
// 05 · routing matrix
Priority beats numbering: semantic intent wins over tool names. Rules are listed in scoring priority order; R0 catches anything unmatched.
41 of 41 rules shown · ordered by the same priority array the CLI router uses.
// 06 · scenarios
Each scenario is a skill module with its own methodology, required tools, and evidence format.
jadx · apktool · smali
Static + dynamic Android analysis
Frida · Objection · MobSF
IPA and runtime instrumentation
IDA · radare2 · Ghidra
exe / dll / so / elf / mach-o
dnSpy · de4dot
Managed assemblies and obfuscators
jshook · CDP
Signatures and encrypted parameters
opcode VM analysis
Custom risk-control virtual machines
BurpSuite · Reqable MCP
Traffic capture and replay
YARA · sandbox
Static, dynamic, and behavioral triage
Nmap · Nuclei · SQLMap
Authorized assessment pipelines
red-team orchestration
Recon through lateral movement
40+ sub-skills sandbox
Competition-ready playbooks
binwalk · emba
Extraction and embedded analysis
BinDiff
Version deltas and repro
ROP · heap
Exploit development chains
ETW · AMSI research
Authorized environment studies
audit tooling
Interface and authz review
trivy · gitleaks · syft
SBOM and dependency review
garak · prompt tooling
Injection and agent abuse
angr · unicorn
Obfuscation and anti-debug
mermaid · graphviz
Evidence visualization
// 07 · quickstart
You don't run the workflow — your agent does. You provide the repo, a startup prompt, and an authorized task.
Java / JDK — jadx and apktool
Node.js 22.12+ — JS toolchain and MCP servers
Python 3.x — Frida and helper scripts
An AI coding agent — Claude Code, Codex, Cursor, OpenCode…
Open the repo and let your agent read README_AI.md.
Give it an authorized task. Initialization, routing, tool checks, and reporting are all automatic.
git clone https://github.com/zhaoxuya520/reverse-skillRead README_AI.md fully and follow its section 0 to initialize this environment automatically. Run normal steps on your own; only ask me for authorization, credentials, commercial licenses, or anything that changes external state. Report the platform you detected, the rules chain, and the tool index status, then continue with the tasks I give you."Analyze the encryption protocol in this APK."That's it. The agent detects your platform, refreshes the tool index, loads the rules chain, and routes — everything the tutorial shows step by step, with example paths and troubleshooting.
// 08 · safety
This project ships reverse engineering, hooking, scanning, and CTF tooling. Heuristic engines can flag it — a detection is not automatically proof of malware, and it is not proof of safety either.
If a scanner or EDR fires on this project, don't panic and don't auto-approve. Work through these checks:
Download only from the official repository or releases, and check the version, commit, and file hashes.
Read what was flagged and the recent diffs around it. Don't whitelist the whole directory on a hunch.
Use a throwaway VM or sandbox with least privilege and a restricted network when working with samples.
Send the security product name, detection label, relative path, SHA-256, project version, and download source.
// 09 · contributors
The maintainers and contributors of the upstream project, synced live from GitHub.
// 10 · sponsors
These organizations fund the maintenance of the routing benchmarks, cross-platform CI, and the public security workflow library.
// 11 · contact
Technical discussion and community support — pick whichever channel works for you.
Paste a real task into the router and watch it land on the right playbook — same engine, same rules, right in your browser.