agentleFS
ajtazerajtazer/heckit/skills/cve-hunting/cve-hunting-methodology/SKILL.md

cve-hunting-methodology

Skill2 starsChanged 2 months agoMITView on GitHub

Cross-cutting methodology for the CVE-hunting pipeline (ported from find-cve-agent): when a bug is design-vs-real, false-positive avoidance, version checking before reporting, responsible disclosure norms, acceptance-rate expectations per vuln class, vulnerability chaining playbook, known false-positive patterns, maintainer-response patterns, secure-pattern reference (what NOT to flag), and a self-criticism checklist to run before claiming a finding. Use this alongside the cve-hunter/cve-exploiter/cve-validator agents and the /cve-hunt pipeline — load it whenever judging if a finding is real, worth reporting, or already fixed.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before the cve-validator agent signs off on a finding → read false-positive-avoidance.md + self-criticism-checklist.md.

    line 27
  2. Very specific:

    Before picking a target category in /cve-recon → read acceptance-rates.md.

    line 28
  3. Very specific:

    After confirming one bug → read chaining-playbook.md before stopping.

    line 29
  4. Very specific:

    Before drafting a disclosure → read disclosure-channels.md + responsible-disclosure.md.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CVE Hunting Methodology

Reference material for judgment calls during the CVE-hunting pipeline (/cve-recon → /cve-hunt → cve-hunter → cve-exploiter → cve-validator → /cve-registry). This skill has no scripts to run — it's the accumulated judgment layer. Read the relevant reference file at the matching decision point:

Rules (apply before calling anything a finding)

  • references/design-vs-bug.md — is this actually a bug, or intended behavior/documented limitation?
  • references/false-positive-avoidance.md — the checks to run before writing up a finding
  • references/version-checking.md — confirm the vulnerable code path still exists in the current released version, not just in history

Knowledge (context for prioritization and write-ups)

  • references/acceptance-rates.md — which vuln classes actually get accepted/paid, to prioritize hunting effort
  • references/chaining-playbook.md — how to escalate a low-impact finding into something that matters by chaining
  • references/false-positive-patterns.md — catalog of common FP shapes per vuln class
  • references/rejection-taxonomy.md — why maintainers/triagers reject reports, categorized
  • references/maintainer-responses.md — patterns in how maintainers respond, and how to read them
  • references/secure-patterns.md — code patterns that are ALREADY safe — don't flag these
  • references/self-criticism-checklist.md — devil's-advocate pass to run on yourself before submitting a verdict
  • references/disclosure-channels.md — picking HackerOne vs GHSA vs direct email vs full disclosure
  • references/responsible-disclosure.md — timelines and etiquette for coordinated disclosure

When to use this

  • Before the cve-validator agent signs off on a finding → read false-positive-avoidance.md + self-criticism-checklist.md.
  • Before picking a target category in /cve-recon → read acceptance-rates.md.
  • After confirming one bug → read chaining-playbook.md before stopping.
  • Before drafting a disclosure → read disclosure-channels.md + responsible-disclosure.md.

Download now (ZIP)

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.