agentleFS
Lu1sDVLu1sDV/skillsmd/vuln-research/SKILL.md

vuln-research

Skill2 starsChanged 12 days agoNo licenceView on GitHub

Use when performing security-focused vulnerability research, bug bounty hunting, penetration testing, or exploit development on a specific target codebase or binary. Covers taint analysis across 30+ attack domains, sink analysis for 10+ languages, SAST/DAST integration, agent sweep, DuckDB-persisted phase pipeline, fuzzing harness, stateful fuzzing, directed symbolic execution, history-driven fuzzing, FuzzGPT, generate edge-case test programs, differential / metamorphic oracle, continuous / perpetual / self-firing vuln discovery, keep hunting until N high/critical confirmed, patch diffing, supply chain attack surface, find me zero days, sweep everything, memory corruption, ROP, firmware audit, kernel driver. SKIP for: generic code reading, writing new features, refactoring, single-diff review without a security goal, or infra config not being audited for vulnerabilities — use code-review or a general coding skill instead.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 0 are common, 13 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 13

    Distinctive

    This author's own choices. Worth a look.

  • 2

    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 3 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.