pentest-runbook

Orchestrates an end-to-end authorized Android APK pentest pipeline across four staged skills.

48|27|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/abisheikM1/Tribunal --skill pentest-runbook-abisheikm1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pentest-runbook
Source: https://github.com/abisheikM1/Tribunal/tree/main/skills/pentest-runbook
Command: npx skills add https://github.com/abisheikM1/Tribunal --skill pentest-runbook-abisheikm1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a full Android app pentest requires coordinating static decompilation, dynamic emulator verification, API testing, and finding validation as separate manual steps; this Skill chains them into one autonomous, resumable pipeline keyed by the APK's SHA-256. ## Core Features & Use Cases - Four-stage orchestration: Drives decompile-threat-review, dynamic-verify, api-vuln-test, and courtroom-verdict back-to-back with no manual gate, passing structured JSON through targets/<apk-sha256>/. - Preflight gating: Runs preflight_check.py before static and dynamic stages so missing tools (adb, frida-server, emulator, Burp) stop the run instead of failing mid-stage. - Adversarial validation: Every confirmed finding goes through a prosecution/defense/judge trial, and only guilty verdicts produce final reports under report/<package>/. - Use Case: Drop an authorized APK into apk/ and say "run the full pipeline" — the Skill decompiles it, builds a threat model, verifies findings on your emulator, tests the API surface, and writes courtroom-vetted vulnerability reports. ## Quick Start Drop your authorized APK into the apk/ folder and ask the agent to run the full pentest pipeline end to end on it.

Frequently Asked Questions about pentest-runbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a full Android APK pentest automatically?

Place the authorized APK in the apk/ directory and trigger the runbook; it executes decompile-threat-review, dynamic-verify, api-vuln-test, and courtroom-verdict in sequence with no manual gates. State is stored in targets/<apk-sha256>/ so interrupted runs resume by re-running a stage.

What tools are required for Android dynamic app testing?

The pipeline requires apktool and jadx for decompilation, adb, frida with frida-server, and objection for instrumentation, plus Burp Suite and an Android Studio emulator for traffic interception. Python 3.10+ runs the bundled scripts, and preflight_check.py verifies readiness before each stage.

How does the pipeline handle SSL pinning bypass on Android?

It first tries a generic bypass such as objection's android sslpinning disable command. If that fails, a dedicated subagent reads the pinning details in threat_model.json and writes a tailored Frida hook saved as frida/bypass.js for reuse in API testing.

Can I resume an interrupted Android pentest run?

Yes, all stage outputs live in targets/<apk-sha256>/ as JSON files, so re-running any stage against the same hash resumes where it stopped. The courtroom-verdict stage skips findings that already carry a courtroom_verdict, so decided cases are never re-litigated.

What are the scope and authorization limits of this pentest pipeline?

An APK is in scope only if it physically resides in the apk/ directory, which serves as the operator's assertion of ownership or authorization. Scripts fail closed on the resolved path, and the pipeline is intended strictly for authorized testing of your own applications.