Curate hackmode-scripts into the monorepo #10

Merged
lost-rob0t merged 1 commit from agent/curate-hackmode-scripts into master 2026-08-16 05:14:34 +00:00
lost-rob0t commented 2026-08-16 05:12:10 +00:00 (Migrated from github.com)

Summary

Completes the source-curation portion of #5 without importing generated junk or turning legacy shell glue into runtime architecture.

Migrated as non-executable reference source

Under tools/legacy/recon/:

  • alt.py
  • bbot.sh
  • dex.sh
  • dns-up.sh
  • dork.sh
  • parse-nmap.py
  • photon-scan.sh

Each has an explicit actor/provider port target in tools/legacy/recon/README.org and docs/migration/hackmode-scripts.org.

Intentionally rejected

  • generated ralp binaries and FASLs
  • credential-hunting git-dorks.sh
  • cracking helpers
  • direct BBRF state wrappers
  • malformed/incomplete rules prototypes mixed with generated artifacts

Safety / architecture

Legacy files are committed mode 100644, are not installed or invoked, and CI rejects executable files under tools/legacy/. Future ports must emit typed assets through the canonical Hackmode operation/asset protocol rather than recreate file/FIFO state.

Verification

  • no generated binary/FASL artifacts added
  • no file under tools/legacy is executable
  • migration manifest records retained and rejected material
  • existing monorepo hygiene/Emacs checks remain enabled

Closes #5.

## Summary Completes the source-curation portion of #5 without importing generated junk or turning legacy shell glue into runtime architecture. ### Migrated as non-executable reference source Under `tools/legacy/recon/`: - `alt.py` - `bbot.sh` - `dex.sh` - `dns-up.sh` - `dork.sh` - `parse-nmap.py` - `photon-scan.sh` Each has an explicit actor/provider port target in `tools/legacy/recon/README.org` and `docs/migration/hackmode-scripts.org`. ### Intentionally rejected - generated `ralp` binaries and FASLs - credential-hunting `git-dorks.sh` - cracking helpers - direct BBRF state wrappers - malformed/incomplete rules prototypes mixed with generated artifacts ### Safety / architecture Legacy files are committed mode `100644`, are not installed or invoked, and CI rejects executable files under `tools/legacy/`. Future ports must emit typed assets through the canonical Hackmode operation/asset protocol rather than recreate file/FIFO state. ## Verification - no generated binary/FASL artifacts added - no file under `tools/legacy` is executable - migration manifest records retained and rejected material - existing monorepo hygiene/Emacs checks remain enabled Closes #5.
Sign in to join this conversation.
No description provided.