path-tracing-reverse

Reverse engineer compiled binaries into functionally identical source code.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Zurybr/lefarma-skills --skill path-tracing-reverse-zurybr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: path-tracing-reverse
Source: https://github.com/Zurybr/lefarma-skills/tree/main/letta/benchmarks/trajectory-only/path-tracing-reverse
Command: npx skills add https://github.com/Zurybr/lefarma-skills --skill path-tracing-reverse-zurybr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables the precise reverse engineering of compiled binaries to generate functionally identical source code, crucial for tasks requiring exact output reproduction.

Core Features & Use Cases

  • Binary Analysis: Systematically disassemble and analyze compiled executables.
  • Constant Extraction: Identify and decode all floating-point and integer constants.
  • Algorithm Reconstruction: Methodically recreate the original program logic.
  • Output Verification: Ensure byte-for-byte identical output compared to the original binary.
  • Use Case: Recovering lost source code for a critical graphics rendering application where pixel-perfect output is non-negotiable.

Quick Start

Use the path-tracing-reverse skill to analyze the binary 'mystery' and generate equivalent source code.

Frequently Asked Questions about path-tracing-reverse

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

FAQPage Schema
How do I reconstruct source code from a compiled binary?

Source code reconstruction from a compiled binary requires disassembling the executable, extracting embedded constants, methodically recreating the program logic, and verifying output for byte-for-byte or pixel-perfect identical execution results.

What is the best way to recover lost source code for a graphics application?

Recovering lost source code for graphics applications demands exact output reproduction by analyzing binary structures, decoding floating-point constants, and incrementally verifying that the reconstructed algorithm yields pixel-perfect results compared to the original binary execution.

Can I extract floating-point and integer constants from compiled executables?

Yes, constant extraction is a core feature of binary analysis that identifies and decodes all floating-point and integer constants embedded within compiled executables to ensure functional identity during algorithm reconstruction.

How does binary analysis ensure byte-for-byte identical output?

Binary analysis ensures byte-for-byte identical output by systematically disassembling the executable, analyzing output formats and binary structures, recreating the original logic, and performing incremental verification against the original execution results.

When do I need to reverse engineer compiled binaries for exact output reproduction?

Reverse engineering compiled binaries for exact output reproduction is necessary when recovering proprietary algorithms or lost source code where pixel-perfect or byte-for-byte replication of the original execution results is strictly required.

What are the limitations of algorithm reconstruction from binaries?

Algorithm reconstruction from binaries requires detailed analysis of output formats and binary structures, relying on incremental verification to achieve functional identity, which may be limited by complex proprietary logic or heavily obfuscated code patterns.