analyze-module

Analyze loaded modules to extract exports, RTTI data, strings, and function references.

15|4|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/vzco/arc-probe --skill analyze-module
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-module
Source: https://github.com/vzco/arc-probe/tree/main/plugins/arc-probe/skills/analyze-module
Command: npx skills add https://github.com/vzco/arc-probe --skill analyze-module

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep analysis of a loaded module in the target process to enumerate exports, RTTI classes, strings, and key functions.

Core Features & Use Cases

  • Export table enumeration and reporting
  • RTTI-based class discovery and hierarchy reconstruction
  • String reference discovery with cross-reference context
  • Identification of notable functions and entry points
  • Structured reporting suitable for tooling and human review

Quick Start

Analyze a target module by name (e.g., "target.dll") to initiate an automated analysis of exports, RTTI, strings, and function references.

Frequently Asked Questions about analyze-module

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

FAQPage Schema
How do I enumerate exports and reconstruct RTTI class hierarchies from a loaded DLL?

To enumerate exports and reconstruct RTTI class hierarchies from a loaded DLL, you analyze the module's PE headers and RTTI descriptors to extract API tables and class relationships. This process provides structured reporting of the module's underlying architecture.

What is the best way to find string references and key functions during reverse engineering?

Finding string references and key functions during reverse engineering involves scanning the loaded module to discover text references with cross-reference context. This identifies notable entry points and provides structured data suitable for both tooling and human review.

Can I analyze a loaded module's RTTI data without external probe tools?

You cannot analyze a loaded module's RTTI data without external probe tools, as this process requires host tooling such as probe_modules, probe_pattern_scan, or probe_dump. These tools are necessary to access the target process and parse the required PE headers and RTTI descriptors.

How do I extract RTTI data and exports from a target process automatically?

To extract RTTI data and exports from a target process automatically, you initiate an automated analysis by specifying the target module name, such as target.dll. The system then parses the loaded module to extract exports, class hierarchies, and string references.

Does this module analysis approach work for understanding C++ class structures in memory?

Yes, this module analysis approach works for understanding C++ class structures in memory by leveraging RTTI-based class discovery. It parses RTTI descriptors within the loaded target process to reconstruct the class hierarchy and identify object relationships.