Bug Bounty Methodology

Bug Bounty Methodology is a Quality skill for Claude Code, published by elementalsouls in Claude-BugHunter.

3.6K stars559 forkson elementalsouls/Claude-BugHunterAdded 2026/08/16+3% in starsRepository updated 2026/08/16

ai-securityanthropicapplication-securitybug-bountybugbountybugcrowdclaudeclaude-codeclaude-skillsethical-hackinghackeroneoffensive-securitypentestingred-teamsecurity-toolsweb-security

Install in seconds

Install Bug Bounty Methodology

Copy Bug Bounty Methodology into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/elementalsouls/Claude-BugHunter/tree/main/skills/bb-methodology ~/.claude/skills/bb-methodology

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/elementalsouls/Claude-BugHunter.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/bb-methodology/SKILL.md in elementalsouls/Claude-BugHunter
Installs to: ~/.claude/skills/bb-methodology
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1354 skills

What Bug Bounty Methodology does

Bug Bounty Methodology orchestrates bug bounty hunting sessions by combining a five-phase non-linear workflow with critical thinking tactics like developer psychology, anomaly detection, and what-if experiments to decide next steps.

Bug Bounty Methodology is cataloged under Quality on DirSkills. Bug Bounty Methodology comes from a repository tagged ai-security, anthropic, application-security, bug-bounty and bugbounty.

Documentation

README

Excerpt

Bug Bounty Methodology: Workflow + Mindset

Master orchestrator for hunting sessions. Combines the 5-phase non-linear workflow with the critical thinking framework that separates top 1% hunters from the rest.

PART 0: MODE CONFIRMATION (Before Anything Else)

Confirm the engagement type before deciding what counts as a finding. The same target produces a different report shape depending on which mode applies. Getting this wrong is the single biggest waste of time in this workflow — answer it explicitly before Phase 0.

This is the opening of the README. Read the full README on GitHub.

Commands Bug Bounty Methodology provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

/dashboard
/recon
/validate
/triage
/report
/remember

Frequently asked about Bug Bounty Methodology

What else does elementalsouls publish alongside Bug Bounty Methodology?
Bug Bounty Methodology is one of 25 skills that DirSkills catalogs from elementalsouls/Claude-BugHunter, the repository it ships in. Its siblings there include API Misconfig Hunter, APK Red Team Pipeline and Auth Bypass Hunting. Each one is a separate skill with its own page in this directory, installs the same way Bug Bounty Methodology does, and is maintained by elementalsouls in that same repository. The rest of the collection is listed on the elementalsouls/Claude-BugHunter page.
How does Bug Bounty Methodology compare to other Quality skills?
Bug Bounty Methodology ranks #369 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Bug Bounty Methodology against them. Open each page to compare what they document and how they install.