bug-bounty

Guides end-to-end bug bounty workflows from recon through vulnerability hunting to report writing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security researchers waste time on theoretical bugs, shallow recon, and rejected reports. This Skill provides a structured bug bounty methodology covering recon, vulnerability hunting, validation, and report writing so hunters focus on exploitable, payable findings. ## Core Features & Use Cases - Full Recon Pipeline: Subdomain enumeration, live host probing, URL collection, cloud asset discovery, and HackerOne scope retrieval using tools like subfinder, httpx, nuclei, and ffuf. - Vulnerability Hunting Checklists: Detailed testing procedures for IDOR, SSRF, XSS, SQLi, OAuth/OIDC, GraphQL, race conditions, file upload, business logic, and LLM/AI security issues, including bypass tables and A-to-B bug chaining methods. - Validation & Reporting: A 7-Question Gate to kill weak findings, CVSS 3.1 scoring guidance, and report templates by vulnerability class. - Use Case: Starting on a new HackerOne program, use the Skill to pull the program scope, run the standard recon pipeline, hunt IDOR variants across API endpoints with two test accounts, then validate and write a submission-ready report. ## Quick Start Use the bug-bounty skill to start recon and plan a hunting session for the target program example.com on HackerOne.

Frequently Asked Questions about bug-bounty

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

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

Begin with the recon pipeline: enumerate subdomains with subfinder and assetfinder, probe live hosts with httpx, collect URLs via katana and waybackurls, then run nuclei for known issues. Read the program scope first and check disclosed reports before hunting.

How do I test for IDOR vulnerabilities in APIs?

Create two accounts, capture all object IDs in requests as one user, then replay those requests with the other user's session. Test all IDOR variants including body parameters, GraphQL node queries, batch endpoints, nested paths, and method swaps like PUT and DELETE.

What tools are needed for bug bounty recon?

Core Go tools include subfinder, httpx, dnsx, nuclei, katana, ffuf, and waybackurls. Optional additions are sqlmap for SQL injection, trufflehog for secret scanning, semgrep for static analysis, and subzy for subdomain takeover checks.

When should I not submit a vulnerability report?

Do not submit theoretical bugs without demonstrated impact, DNS-only SSRF callbacks, open redirects without an account takeover chain, or source maps without secrets. The Skill's 7-Question Gate requires proving real harm like stolen funds, leaked PII, or account takeover before writing.

Does this methodology cover LLM and AI feature testing?

Yes, it includes checklists for prompt injection, indirect injection via processed documents, chatbot conversation IDOR, system prompt extraction, code execution tool abuse, and agentic AI risks mapped to OWASP ASI01-ASI10 categories.