What problem does it solve? Reverse engineering frontend JavaScript signature and encryption logic often fails because analysts guess at browser environments instead of working from observed evidence. This Skill enforces a disciplined, evidence-first workflow for locating signature chains, capturing runtime data, and reproducing target parameters locally in Node. ## Core Features & Use Cases - Five-Phase Workflow: Structures work into Observe, Capture, Rebuild, Patch, and DeepDive stages so page evidence always precedes local environment patching. - Task-Driven MCP Tool Routing: Directs the agent to the correct reverse-task tools (start_reverse_task, manage_reverse_task, orchestrate_reverse_task, run_reverse_agent, export_portable_bundle) based on user intent. - Environment Patching Discipline: Drives Node environment rebuilding via proxy env logs, first-divergence tracking, and minimal causal-unit patches rather than blind browser simulation. - Use Case: When asked to reproduce a site's request signature (e.g., an h5st or X-Bogus parameter), the agent hooks fetch/xhr in the page, exports a rebuild bundle, patches the Node environment iteratively, and optionally proceeds to AST deobfuscation or VMP instrumentation. ## Quick Start Use the jsreverser-mcp-playbook to reverse engineer the signature generation logic of the target site, starting a new reverse task and following the observe-capture-rebuild-patch workflow.
