hypothesis-agent

Generate 5–10 endpoint-level attack hypotheses from bug bounty recon files.

Updated May 14, 2026
One-click install
npx skills add https://github.com/cuongnguyen-git/bug-bounty --skill hypothesis-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hypothesis-agent
Source: https://github.com/cuongnguyen-git/bug-bounty/tree/main/.claude/skills/hypothesis-agent
Command: npx skills add https://github.com/cuongnguyen-git/bug-bounty --skill hypothesis-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts messy bug bounty reconnaissance into specific, high-value attack hypotheses you can test next, without wasting time on low-payoff or scanner-obvious ideas.

Core Features & Use Cases

  • Recon-to-hypotheses generation: Reads all recon files in a target directory and produces 5–10 hypotheses tied to concrete endpoints, parameters, and flows.
  • Hard-stop quality filtering: Discards informational-only, theoretical, scanner-catchable, missing-header, best-practice, public-data, and low-severity vectors before output.
  • Self-learning noise reduction: Checks weak-pattern and recon-noise logs to avoid repeating known time-wasters, then logs discarded classes after generation.
  • Adversarial review and prioritization: Applies a structured thinking process (assumptions, trust boundaries, break conditions, exact test locations) and ranks hypotheses by uniqueness and duplicate risk.

Quick Start

Run the hypothesis-agent with your recon directory path so it reads the recon files and returns 5–10 concrete attack hypotheses tailored to that target.

Frequently Asked Questions about hypothesis-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate attack hypotheses from bug bounty recon data?

To generate attack hypotheses from bug bounty recon data, you provide a directory of recon files containing endpoints, parameters, and authentication flows. The system reads these files and outputs 5–10 concrete, testable attack ideas prioritized by uniqueness and severity.

What is the best way to filter out low-value vulnerability findings from recon?

The best way to filter low-value vulnerability findings from recon is using hard-stop quality filters. This mechanism discards scanner-obvious, missing-header, and public-data vectors before outputting attack hypotheses, ensuring you only test high-payoff targets.

Can I turn endpoint and API route data into testable bug bounty ideas?

Yes, you can turn endpoint and API route data into testable bug bounty ideas. By analyzing observed behaviors and authentication flows from your recon files, the system derives specific attack mechanics, trust boundaries, and exact test locations for vulnerability discovery.

How does an attack hypothesis agent handle duplicate vulnerability reports?

An attack hypothesis agent handles duplicate vulnerability reports by applying an adversarial review process. It checks weak-pattern and recon-noise logs to avoid repeating known time-wasters, then ranks generated hypotheses by uniqueness and duplicate risk.

Do I need to format recon files specifically for endpoint testing hypothesis generation?

You do not need to format recon files specifically for endpoint testing hypothesis generation. The system reads all files directly from the provided target directory, utilizing raw endpoints, parameters, and authentication flow data without requiring strict preprocessing.