bb-local-toolkit is a skill for Claude that covers the whole bug bounty cycle in one document: recon, pre-hunt research, hunting, validation and reporting. Its opening rules push the agent to read the full program scope first, to prove real impact and to drop theoretical findings early.
It adds a tools section with install notes and command patterns for recon utilities, fuzzers, static analysis and scanners, plus checklists for common bug classes such as IDOR, SSRF, OAuth, race conditions, GraphQL and CI/CD pipelines. It is meant for assets covered by a program you have joined.
What You Get
- A set of working rules such as read the scope first, stop after five empty minutes and switch targets after an hour
- A method for chaining one finding into related ones, with a table of common chains
- Checklists for IDOR, SSRF, OAuth, file upload, race conditions, business logic, XSS, SQL injection, GraphQL and more
- A seven-question gate and four pre-submission gates to run before writing a report
- Tool notes for subdomain discovery, fuzzing, static analysis and secret scanning
Common Use Cases
- Starting a new bug bounty target and wanting one document for the whole session
- Deciding whether a half-confirmed finding is worth a report
- Looking up how to call a recon tool or wordlist already installed locally
What Makes It Unique
It combines the workflow with a tool map in a single skill, so the agent can pick the right local wordlist or binary without a separate lookup. Its rules are blunt about wasted time: theoretical bugs are dropped, shallow recon loops are cut short and chains are reported as one finding.
Under The Hood
The skill is one long SKILL.md of instructions with no bundled scripts. Following it, the agent runs shell commands for recon and testing, such as subdomain discovery, URL collection, fuzzing, static analysis with semgrep and secret scanning, and it sends requests to the target hosts and to public sources like scope pages and certificate logs. It writes output files and notes to the working folder, clones repositories with git, and its install notes fetch tools from the network. The text also covers credentials: it shows patterns for finding leaked keys and tokens and tells the agent to prove what a found key can reach. One section describes prompt-injection risks in CI/CD workflows, so the file quotes injection phrases as examples. Run it only against assets you are authorized to test.