reconstruct-types

A command that rebuilds C and C++ structure or class definitions from a compiled module's decompiled code. It creates C++ header files and marks how confident it is in each field.

In plain words
What is it for?
Reconstruct types from a module such as a Windows DLL, rebuild a named class, include COM interfaces, and check the result against assembly code.
Why use it?
It helps recover usable type definitions when the original source code is unavailable.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/marcosd4h/deepextractruntime/reconstruct-types
Clone the repo
git clone --depth 1 https://github.com/marcosd4h/DeepExtractRuntime
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,255 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01255
Opus 5 $0.00000 $0.00628
Sonnet 5 $0.00000 $0.00251
Haiku 4.5 $0.00000 $0.00126

Measured 2d ago against content hash 3d954d2c2223, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

reconstruct-types scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/reconstruct-types.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Reconstruct Types

Overview

Reconstruct C/C++ struct and class definitions from a module's decompiled code by scanning memory access patterns, vtable contexts, and mangled names across all functions. Generates compilable C++ header files with per-field confidence annotations.

The text after /reconstruct-types specifies a module and optionally a class name:

  • /reconstruct-types appinfo.dll -- reconstruct all types in the module
  • /reconstruct-types appinfo.dll CSecurityDescriptor -- reconstruct a specific class
  • /reconstruct-types appinfo.dll --include-com -- include COM interface reconstruction
  • /reconstruct-types appinfo.dll --validate -- validate generated header against assembly

IMPORTANT: Execution Model

This is an execute-immediately command. Do NOT present anything for user confirmation. Run and write the final reconstructed types straight to the chat as your response. The user expects to see the completed output.

Workspace Protocol

This command uses the type-reconstructor agent's reconstruct_all.py pipeline, plus optional validation:

  1. Create .claude/workspace/<module>_reconstruct_types_<timestamp>/.
  2. Pass --workspace-dir <run_dir> and --workspace-step reconstruct to the reconstruct_all.py invocation.
  3. Keep only summary output in context; read full intermediate data from <run_dir>/reconstruct/results.json when presenting results.
  4. Use <run_dir>/manifest.json to track completed/failed steps.

Execution Context

IMPORTANT: Any inline Python that imports helpers.* must run with cd <workspace>/.claude (so the .claude/ directory is on sys.path), not from the workspace root. Script invocations like python .claude/skills/.../script.py can be run from the workspace root because those scripts manage their own path setup.

Steps

Step 0: Preflight Validation

Validate arguments using helpers.command_validation.validate_command_args("reconstruct-types", {"module": "<module>"}). If validation fails, report the errors and stop. On success, use result.resolved["db_path"] for subsequent script calls.

Read the full file on GitHub · 103 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 103 lines · 0 tokens per session scan A 3d954d2c2223

Subscribe to this mod's changes

reconstruct-types is a command published in the GitHub repository marcosd4h/DeepExtractRuntime (20 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,255 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.