maxtac-android-runtime-debugging

Capture Android runtime evidence via ADB, logcat, JDWP, and Frida.

12|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/philo-groves/MaxTAC --skill maxtac-android-runtime-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maxtac-android-runtime-debugging
Source: https://github.com/philo-groves/MaxTAC/tree/main/plugins/maxtac-android/skills/maxtac-android-runtime-debugging
Command: npx skills add https://github.com/philo-groves/MaxTAC --skill maxtac-android-runtime-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires adb, frida, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill facilitates authorized Android runtime observation and proof collection, streamlining the process of capturing evidence for security research.

Core Features & Use Cases

  • Runtime Observation: Monitor and capture ADB, logcat, JDWP, Frida, component launch, content-provider probing, appops, dumpsys, and runtime evidence.
  • Evidence Capture: Utilize Core proof folders for durable evidence capture, including raw command output, logs, screenshots, recordings, scripts, inputs, and package metadata.
  • Component and IPC Probes: Safely launch activities and send broadcasts, probe content providers, and use Binder or service hypotheses with caution.
  • JDWP and Debuggable Apps: Attach to debuggable targets, record debugger attachment requirements, and manage debugger-dependent evidence.
  • Frida on Android: Employ Frida for hooks, Java method observation, native JNI tracing, and targeted runtime state checks.
  • Output: Persist device/API state, metadata, logs, Frida/JDWP scripts, content-provider outputs, and raw errors, and prepare concise handoffs to auditors.

Quick Start

Run the maxtac-android-runtime-debugging skill to capture runtime evidence for the package 'com.example.app'.

Frequently Asked Questions about maxtac-android-runtime-debugging

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

FAQPage Schema
How do I capture Android runtime evidence for security research using ADB and Frida?

You can capture Android runtime evidence by observing logcat, JDWP, and Frida hooks, then persisting raw command outputs, logs, and scripts into durable proof folders for auditor handoffs.

What is the best way to monitor Android content providers and IPC components safely?

Monitoring Android content providers involves safely launching activities, sending broadcasts, and probing Binder service hypotheses while capturing raw outputs and metadata as runtime evidence.

Can I attach Frida to debuggable Android apps to trace Java methods and native JNI calls?

Yes, Frida attaches to debuggable Android targets to perform Java method observation, native JNI tracing, and targeted runtime state checks, recording debugger-dependent evidence for analysis.

Do I need ADB and Frida tools installed to observe Android appops and dumpsys state?

Yes, ADB and Frida are required dependencies for runtime analysis, enabling you to capture appops, dumpsys outputs, package metadata, and device API state during security research.

Why does JDWP debugging require debuggable targets for Android runtime observation?

JDWP debugging requires debuggable targets because the Java Debug Wire Protocol needs specific application configurations to attach and manage debugger-dependent evidence properly.