bug-hunting
Skill4 starsChanged 8 months agoMITView on GitHub
End-to-end bug bounty phase flow for BearStrike AI.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Quad4-Software/skillstheir own version, first seen Oct 3, 2026
- m4vic/bug-huntingtheir own version, first seen Aug 25, 2026
- Aceproulx/claude-skillstheir own version, first seen Jul 7, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- m4vic/bug-hunting★ 10same name
- Aceproulx/claude-skills★ 1same name
- Quad4-Software/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- exploitationSkill
- pentest-toolsSkill
- planningSkill
- reconSkill
- reportingSkill
- research-notesSkill
- traffic-proxySkill
- xray-suiteSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this flow for authorized bug bounty targets.
- Distinctive: line 17
Stop noisy scans when WAF is detected and switch to low-rate mode.
- Distinctive: line 29
Use this loop to reduce noise and token burn:
- Distinctive: line 31
Test authorization boundaries first.
- Distinctive: line 46
Do not continue to next hypothesis until current one has:
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
bug-hunting
Use this flow for authorized bug bounty targets.
State machine
RECON -> ENUM -> VULN -> VERIFY -> REPORT
Rules
- Stay in scope at every step.
- Stop noisy scans when WAF is detected and switch to low-rate mode.
- Confirm findings manually before report generation.
Recommended sequence
- recon skill to map hosts and services.
- pentest-tools skill to choose matching tools per target type.
- exploitation skill only after strong signals.
- reporting skill to produce final markdown package.
Bug-hunt loop (efficient mode)
Use this loop to reduce noise and token burn:
- Build endpoint shortlist by business impact.
- Test authorization boundaries first.
- Validate one strong signal to completion.
- Expand only if evidence quality remains high.
Where bugs are often found
Focus checks on:
- ID fields in REST/JSON APIs
- GraphQL object queries and mutations
- Mobile/web API parity gaps
- Multi-step flows (cart -> payment -> refund)
- Export/report endpoints leaking cross-tenant data
Quality gate
Do not continue to next hypothesis until current one has:
- baseline response,
- altered request response,
- clear impact statement.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.