reverse-and-harden
Skill18 starsChanged 2 days agoMITView on GitHub
Understand any app or build with REA, then ship your own build hardened with BLA. Use when the task is to figure out how an unfamiliar app, binary, or dependency works, or to prepare a release so a casual AI reverse-engineering pass does not read it trivially.
In this repository6 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- dep-auditSkill
- map-firstSkill
- rea-triageSkill
- release-hardenSkill
- ship-checkSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Write down what the app actually does before you change anything.
- Distinctive: line 44
Only analyze software you own or are authorized to analyze.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Reverse, then harden
Two open-source tools, one loop. REA reads anything; BLA protects what you ship.
1. Understand (REA)
morluto/rea, MIT. Install once per machine:
npx rea-agents setup --client claude-codeThis registers the rea MCP server in ~/.claude.json and the skill in ~/.claude/skills/reverse-engineer-anything. Then, from inside the app folder, ask the agent what the target is and let REA route it (it handles 50+ target kinds: JS/Electron trees, ASAR, APK/IPA, WASM, native binaries, packet captures).
Context note: the full REA catalog is ~170 tools. If it floods context, set REA_MCP_INPUT_SCHEMA_PROFILE=compact and trim families with REA_MCP_TOOL_FAMILIES.
Write down what the app actually does before you change anything.
2. Harden your own release (BLA)
qybaihe/bla, MIT. Before shipping YOUR build:
npx bla-agents harden .It finds the build artifacts (dist/, build/, .asar, .wasm, native binaries), hardens them, verifies the hardened output still behaves the same, and writes .bla-hardened/ plus bla-harden-summary.json. Ship the .bla-hardened/ folder, not the raw build.
--dry-run writes nothing and reports what it would do. Run it first on a real project.
The catch worth knowing: bla lint refuses to finish while a one-line license/secret check is still in the source - it expects you (the agent) to rewrite those yourself first. And no client-side scheme is absolute: keep real secrets on the server.
3. Prove it
Nothing ships until scripts/verify.sh exits 0. The verifier agent runs the hardened build through it and rejects anything unproven.
Scope
Only analyze software you own or are authorized to analyze. Harden only your own builds.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

