fleet-hunt
Skill0 starsChanged 3 months agoNo licenceView on GitHub
XBOW-style FLEET hunt — breadth-first autonomous bug-bounty sweep across MANY authorized HackerOne or BugCrowd programs/assets at once, optimized for throughput × validity (leaderboard volume), not single-target depth. This is the industrial sibling of /bug-hunt: where /bug-hunt is a sniper that goes deep on ONE target over many runs, /fleet-hunt is the fleet that ranks the whole attack surface, scores every host for bug-likelihood (host_scorer.py — WAF/status/auth/ tech/admin-staging signals + clone dedup), fans hunt.sh recon + read-only verification across the top hosts in parallel via the Workflow engine, then runs an adversarial multi-agent VALIDATOR swarm (the XBOW moat) so only reproduced, proven findings reach a ranked submission queue. Wires the real kit: h1_recon.py/bc_recon.py (rank programs) -> h1_program.py/bc_program.py (pull each scope) -> scope_guard -> hunt.sh (recon/--verify) -> host_scorer.py (prioritize) -> triage_leads.py --verify -> report_validator.py -> report drafts. Read-only-first and 00-RoE are absolute; every state-changing request still pauses; NEVER auto-submits. Use when: "fleet hunt", "hunt many programs", "xbow-style", "breadth/volume hunt", "sweep all my programs", "maximize submissions", "bugcrowd fleet hunt", "sweep bugcrowd programs", "/fleet-hunt". NOT for going deep on one chosen target (use /bug-hunt) or auditing your own code (use /security-dude, /vuln-research). Run /pick-program first if you don't yet know which programs.
- Reads credentials
In this repository38 other files it gives its agents.
- aiml-dudeSkill
- back-end-dudeSkill
- be2-code-reviewSkill
- be-code-reviewSkill
- book-to-productSkill
- browseSkill
- bug-finder-dudeSkill
- bug-huntSkill
- checkerSkill
- code-qualitySkill
- contractor-dudeSkill
- cruise-plannerSkill
- debug-dudeSkill
- designer-dudeSkill
- fe-code-reviewSkill
- flight-finderSkill
- front-end-dudeSkill
- general-code-reviewSkill
- h1-reportSkill
- helmSkill
- logo-designSkill
- nextjs-code-reviewSkill
- orchestrateSkill
- pick-programSkill
- plan-dudeSkill
- push-dudeSkill
- qa-dudeSkill
- retro-dudeSkill
- round-trip-stocksSkill
- security-dudeSkill
- seo-dudeSkill
- user-test-2Skill
- user-test-massiveSkill
- user-test-miskariSkill
- user-test-sheevookSkill
- user-testSkill
- user-test-splitsquadSkill
- vuln-researchSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 5 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

