reverse-parity-gate

Compare decrypted outputs against real browser outputs for parity.

3|2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/woxiangyangzhimao/skills --skill reverse-parity-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reverse-parity-gate
Source: https://github.com/woxiangyangzhimao/skills/tree/main/reverse-parity-gate
Command: npx skills add https://github.com/woxiangyangzhimao/skills --skill reverse-parity-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill verifies that the output of decryption matches the output from a real browser, ensuring that the decryption process is correct before delivery.

Core Features & Use Cases

  • Byte-by-byte Comparison: Compares the output of decryption against a real browser to ensure parity.
  • Dynamic Field Analysis: Analyzes and accounts for dynamic fields such as timestamps, random IVs, and nonces.
  • Invisible Trap Checklist: Checks for common issues like Base64 variants, padding, parameter order, and character encoding.
  • Reproducibility Test: Tests the reproducibility of the decryption process to identify hidden inputs.

Quick Start

Run the reverse-parity-gate skill to compare the decrypted output with the real browser output for the 'signer.py' integration.

Frequently Asked Questions about reverse-parity-gate

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

FAQPage Schema
How do I verify decrypted output matches real browser results?

To verify decrypted output matches real browser results, perform a byte-by-byte comparison against real browser samples to ensure delivery parity before signing off.

What is byte-by-byte comparison for decryption validation?

Byte-by-byte comparison for decryption validation is the process of checking decrypted outputs against real browser samples to ensure exact parity and correct decryption.

How do I account for dynamic fields like random IVs during decryption verification?

To account for dynamic fields like random IVs and timestamps during decryption verification, perform dynamic field analysis to isolate and exclude these changing values from parity checks.

Why does my decrypted output differ from the real browser output?

Decrypted output differs from real browser output due to invisible traps like Base64 variants, padding errors, parameter order mismatches, or character encoding issues that require checklist verification.

How do I test decryption reproducibility to find hidden inputs?

To test decryption reproducibility and find hidden inputs, run reproducibility tests that repeatedly process the same input to identify hidden parameters affecting the decryption output.