reverse-engineer-rpilisted

# $reverse-engineer-rpi Reverse-engineer a product into a mechanically verifiable feature inventory + registry + spec set, with optional security-audit artifacts and validation gates. ## Hard Guardrails (MANDATORY) - Only operate on code/binaries you own or have **explicit written authorization** to analyze. - Do not provide steps to bypass protections/ToS or to extract proprietary source code/system prompts from third-party products. - Do not output reconstructed proprietary source or embedded prompts from binaries (index only; redact in reports). - Redact secrets/tokens/keys if encountered; run the secret-scan gate over outputs. - Always separate: **docs say** vs **code proves** vs **hosted/control-plane**. ## One-Command Example ```bash python3 skills/reverse-engineer-rpi/scripts/reverse_engineer_rpi.py ao \ --authorized \ --mode=binary \ --binary-path="$(command -v ao)" \ --output-dir=".agents/research/ao/" ``` If you do not have explicit written authorization to analyze that binary, do not run the above. Use the included demo fixture instead (see Self-Test below). Repo-only example (no binary required): ```bash python3 skills/reverse-engineer-rpi/scripts/reverse_engineer_rpi.py cc-sdd \ --mode=repo \ --upstream-repo="https://github.com/gotalab/cc-sdd.git" \ --output-dir=".agents/research/cc-sdd/" ``` Pinned clone (reproducible): ```bash python3 skills/reverse-engineer-rpi/scripts/reverse_engineer_rpi.py cc-sdd \ --mode=repo \ --upstream-repo="