agentleFS
Sign inStart free
Nexus-Organization-InfosecNexus-Organization-Infosec/ClaudeSkills/reverse-engineer/SKILL.md

reverse-engineer

Skill1 starsChanged 3 months agoNo licenceView on GitHub

Audit the user's OWN project end-to-end for security vulnerabilities (known-CVE dependencies, injection, unsafe deserialization, command/code execution, path traversal, hardcoded secrets/API keys, weak crypto, TLS bypass, SSRF, XSS) and stability weaknesses (crash points, unhandled errors, missing timeouts, resource leaks, races), rank the findings by real-world severity, then fix them without breaking the app. Use whenever the user invokes /reverse-engineer or asks to "audit my project for security", "find CVEs / vulnerabilities", "harden the app", "protect me from hackers", "pentest my own code", or "make it stable and secure". This is defensive security on the user's own codebase — think like an attacker to find the holes, then patch them. Runs as a parallel red-team when combined with swarm ("reverse-engineer swarm"): multiple agents each attack a different surface of the user's own app, hunt CVEs and vulns, and report back for the controller to merge and fix.

  • Reads credentials
  • Installs packages

We split this skill into the rules it gives an agent

12 rules. 0 are common, 8 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free