agentleFS
Sign inStart free
noamgariani11noamgariani11/claude-skills/skills/bug-hunt/SKILL.md

bug-hunt

Skill0 starsChanged 3 months agoNo licenceView on GitHub

Full-auto authorized bug-bounty hunt against ONE live in-scope target on **HackerOne or BugCrowd**, driven by the program's platform link. Opens by asking for the program URL (e.g. https://hackerone.com/braze_inc or https://bugcrowd.com/shopify) and pulls scope + policy + disclosed history itself via the platform API (h1_program.py for H1, bc_program.py for BC) — only falling back to a manual paste if the program is private/login-walled. Mines the policy for links and pulls the target's own API/product docs (OpenAPI/GraphQL/SDKs/help center) to model the surface — uses AskUserQuestion for every decision after that, and hard-codes the researcher handle as monk11. Wires the repo's real toolkit end-to-end: generates a machine-parseable scope.md + config.env, runs ./hunt.sh (read-only recon, auto-triage), then the "edge" tools that find what the crowd misses — variant_analysis.py, js_diff.py, authz_matrix.py, osv_check.py (n-day SCA: shipped deps -> known CVEs via OSV+KEV+EPSS), version_diff_probe, verb_tamper_probe, jwt_forge, nosql_authz_probe, deser_detect, ssrf_bypass_gen, xxe_ssti_probe, cors_saml_probe, race_probe (--confirm gated), takeover_monitor, response_exposure_scan, graphql_probe harvest, oauth_probe, and the exposed-data toolchain (dump_triage/secret_miner/id_probe/meta_scan/corr_pivot, RoE-capped proof-not-exfil) — then the validator gate and redacted report drafts via report_from_lead.py. Persistent and exhaustive; never sends a state-changing request without approval, never goes out of scope, never auto-submits. Use when: "bug-hunt", "hunt this program", "hunt this HackerOne target", "hunt this BugCrowd target", "hunt bugcrowd program", "bugcrowd hunt", "find reportable bugs", "/bug-hunt". NOT for auditing your own codebase/app (use /security-dude or /bug-finder-dude).

  • Reads credentials

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use learn, ship and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • genomewalkerSkill

    learn

    Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

44 rules. 0 are common, 12 are distinctive, and 32 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 32

    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 measured: kept by at least 6 in 10 of the 19 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free