bb-methodology

Orchestrates bug bounty hunting sessions using a 5-phase workflow and critical thinking framework.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/inventashif/helpful-code-sidekick --skill bb-methodology-inventashif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bb-methodology
Source: https://github.com/inventashif/helpful-code-sidekick/tree/main/scripts/hackerai/skills/bughunter/bb-methodology
Command: npx skills add https://github.com/inventashif/helpful-code-sidekick --skill bb-methodology-inventashif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug bounty hunters often waste time wandering between targets, chasing false positives, or submitting findings that get rejected as informational. This Skill provides a master orchestration workflow that tells you what to do at every stage of a hunting session, how to think like a top-tier hunter, and how to avoid the process mistakes that get findings retracted. ## Core Features & Use Cases - 5-Phase Non-Linear Workflow: Guides you through Recon, Mapping, Vulnerability Discovery, Prove & Escalate, and Validate & Report, with explicit rules for when to jump back between phases. - Engagement Mode Confirmation: Forces an upfront decision between bug bounty, red team, pentest, and internal audit modes so findings match what the platform actually accepts. - False-Positive Prevention Discipline: Enforces marker discipline, body-diff verification, statistical sampling for timing claims, and a shell-loop ban to kill findings that would come back N/A. - Use Case: You start a session on a new HackerOne program and feel lost. The Skill walks you through defining a goal, selecting vuln classes, routing to the right recon tools, and escalating a low-impact XSS into an account takeover chain before writing the report. ## Quick Start Ask the AI to start a bug bounty hunting session on your target and guide you through the methodology phases step by step.

Frequently Asked Questions about bb-methodology

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

FAQPage Schema
How do I start a bug bounty hunting session on a new target?

Begin with Phase 0: define your goal (which CIA impact you want), select 1-2 vulnerability classes like IDOR or XSS, and confirm the engagement type. Then run a wide recon sweep with subdomain enumeration before moving to deep mapping.

What is the difference between bug bounty and red team findings?

Bug bounty accepts only impact-demonstrated bugs with a full chain to attacker-attainable harm, rejecting hygiene issues like missing headers. Red team engagements accept hygiene findings, recon data, and defensive observations as valid deliverables.

How do I avoid false positives when testing for reflection or bypasses?

Use unique random markers of 8+ characters that cannot appear naturally in the target, and verify the marker is absent from baseline responses. For bypass claims, diff the response body against baseline since a 200 status with identical body is not a bypass.

When should I give up on a parameter or endpoint during testing?

Apply the 20-minute rotation rule: if you make no progress on an endpoint in 20 minutes, rotate to the next endpoint, subdomain, or vulnerability class. Set a hard 45-minute limit per parameter to avoid rabbit holes.

How do I escalate a low-impact bug into a critical finding?

Follow the escalation decision tree: chain XSS to session theft or forced email change for account takeover, escalate SSRF to cloud metadata extraction, and combine low-impact bugs with connector gadgets. Minimize attack prerequisites to zero or one click.

Why do timing-based user enumeration claims get rejected?

Single timing outliers are usually network jitter, not signal. Valid claims require at least 10 interleaved trials per group with the suspect mean at least 2 standard deviations above the control mean.