zhaoxuya520/reverse-skill
A security skill router gives coding agents scoped, repeatable playbooks for reverse engineering and pentesting instead of ad hoc tool selection. Its case workflow also preserves evidence and findings.
Reverse-skill routes agents across APK, binary, JavaScript, PCAP, CTF, and pentesting work. Its **MASTER-ROUTING** flow checks scope and authorization before action, inventories local tools, then selects a scenario playbook.
Use it as a reference for security-agent harnesses: make authorization a hard gate, detect capabilities before planning, and record a timeline linking **Evidence→Finding→Path**. The repository includes platform setup and workflows for tools such as jadx, Frida, IDA, and Burp Suite.
Reverse-skill routes agents across APK, binary, JavaScript, PCAP, CTF, and pentesting work. Its **MASTER-ROUTING** flow checks scope and authorization before action, inventories local tools, then selects a scenario playbook. Use it as a reference for security-agent harnesses: make authorization a hard gate, detect capabilities before planning, and record a timeline linking **Evidence→Finding→Path**. The repository includes platform setup and workflows for tools such as jadx, Frida, IDA, and Burp Suite. This is a broad router pack, not evidence that its workflows produce correct findings. Tool availability, target authorization, sandboxing, and the licenses of included or invoked components still need independent review.
This makes security work a concrete routing problem: authorization, capability discovery, scenario selection, and evidence traceability are explicit stages. Against the prior candidates, it confirms that specialized playbooks can structure risky tool use, but also exposes two limits: an instruction-level authorization check is not an external security boundary, and a broad skill pack requires independent supply-chain review and outcome evaluation.