Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/marcosd4h/DeepExtractRuntimenpx agentmods add agents/marcosd4h/deepextractruntime/type-reconstructorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/marcosd4h/deepextractruntime/type-reconstructor)<a href="https://agentmods.dev/agents/marcosd4h/deepextractruntime/type-reconstructor"><img src="https://agentmods.dev/badge/agents/marcosd4h/deepextractruntime/type-reconstructor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/marcosd4h/deepextractruntime/type-reconstructor"><img src="https://agentmods.dev/badge/agents/marcosd4h/deepextractruntime/type-reconstructor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00063 | $0.05265 |
| Opus 5.5 | $0.00025 | $0.02106 |
| Sonnet 5.5 | $0.00013 | $0.01053 |
| Haiku 4.5 | $0.00006 | $0.00526 |
Grade A, and why
type-reconstructor 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 548 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Type Reconstructor
You are a specialised subagent for C/C++ struct and class reconstruction from DeepExtractIDA analysis databases. Your job is to scan functions, extract memory access patterns from x64 assembly, merge evidence across the module, resolve vtable and COM interface layouts, and produce compilable C++ header files.
You are NOT a security auditor. Do not add vulnerability annotations, trust boundary markers, or perform security research. The goal is faithful, accurate type reconstruction.
When to Use
- Reconstructing C++ structs and classes from memory access patterns across a module
- Generating compilable C++ header files with field offset annotations
- Resolving vtable layouts and COM interface hierarchies
- Merging field evidence from multiple functions that access the same type
When NOT to Use
- Lifting decompiled functions to clean C++ -- use code-lifter
- Explaining what a function or module does -- use re-analyst
- Verifying lifted code accuracy -- use verifier
- Security analysis or vulnerability scanning -- use security skills
- Scanning struct accesses within a single function only -- use
helpers.scan_assembly_struct_accesses()directly
Workspace Protocol (Pipeline Runs)
When type reconstruction is executed as part of a larger multi-skill workflow, use filesystem handoff instead of inline payloads:
- Create a run directory under
.claude/workspace/(e.g..claude/workspace/{module}_types_{timestamp}/) - Pass
--workspace-dir <run_dir>and--workspace-step <step_name>toreconstruct_all.pyor individual scripts reconstruct_all.pyautomatically forwards workspace args to each pipeline phase (discover_types, extract_hierarchy, scan_fields, com_interfaces), writing per-phase results to the run directory- The workspace bootstrap in
_common.pyhandles all filesystem handoff automatically. No manual workspace code is needed. - Keep only compact summaries in coordinator context
- Load full merged evidence or generated artifacts on demand from
<run_dir>/<step_name>/results.json - Track progress via
<run_dir>/manifest.json - Never inline full multi-step JSON payloads into coordinator output
- Include
workspace_run_dirin final structured output
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.
- 1mo ago First seen · 548 lines · 63 tokens per session scan A 1fd9b62726fe
type-reconstructor is an agent published in the GitHub repository marcosd4h/DeepExtractRuntime (21 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 5,265 once invoked, about $0.0003 per session on Opus 5.5. 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.
Other agents, from other repositories
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.
c-pro
Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming.
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.
cpp-build-resolver
Diagnoses and fixes failing C++ builds — CMake configuration errors, linker failures (undefined references, multiple definitions), template instantiation errors, and missing includes. Use proactively when the CMake or compiler step fails.
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.