ajtazer/heckit / skills/cve-hunting/cve-hunting-methodology
cve-hunting-methodology
UnverifiedCross-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.
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 findingreferences/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 effortreferences/chaining-playbook.md— how to escalate a low-impact finding into something that matters by chainingreferences/false-positive-patterns.md— catalog of common FP shapes per vuln classreferences/rejection-taxonomy.md— why maintainers/triagers reject reports, categorizedreferences/maintainer-responses.md— patterns in how maintainers respond, and how to read themreferences/secure-patterns.md— code patterns that are ALREADY safe — don't flag thesereferences/self-criticism-checklist.md— devil's-advocate pass to run on yourself before submitting a verdictreferences/disclosure-channels.md— picking HackerOne vs GHSA vs direct email vs full disclosurereferences/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→ readacceptance-rates.md. - After confirming one bug → read
chaining-playbook.mdbefore stopping. - Before drafting a disclosure → read
disclosure-channels.md+responsible-disclosure.md.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |