agentleFS
noamgariani11noamgariani11/claude-skills/skills/pick-program/SKILL.md

pick-program

Skill0 starsChanged 3 months agoNo licenceView on GitHub

Survey HackerOne or BugCrowd and pick the best bug-bounty program to hunt RIGHT NOW — the one with the highest expected (reportable bug × payout × winnability) for monk11 and this repo's toolkit. Queries the platform's public directory API for the live program list + per-program stats (bounty table, participant count, response efficiency, report activity, launch date), cross-checks disclosed-report depth and surface fit, then scores every candidate on a payout × findability × feasibility rubric weighted by what actually pays in 2026 (server-side RCE/auth-bypass/SSRF, business logic, OAuth/SSO, AI/agentic, cloud, mobile) and by where this repo's edge tools (variant_analysis / js_diff / authz_matrix) convert. Outputs a ranked shortlist with per-program rationale + the classes to lead with, then hands the #1 pick to /bug-hunt. Read-only research only — it never sends traffic to a target asset. STARTS by asking PLATFORM (HackerOne or BugCrowd) then TRACK: the **paid** track (bounty programs) or the **VDP** track — no-money Vulnerability Disclosure Programs sourced from *across the whole web* (disclose.io, self-hosted security.txt, OSS SECURITY.md, government, and platform VDPs), ranked by vdp_finder.py for the lesser-known, safe-to-start, low-competition program where a first valid report earns reputation, a CVE, or hall-of-fame credit — the easiest on-ramp into bug bounty. Use when: "pick a program", "what should I hunt", "find a bug bounty program", "best program right now", "where should I spend my time", "find a VDP", "free/no-pay program to start on", "where do I start in bug bounty", "easiest program to get a bug", "bugcrowd program", "pick a bugcrowd program", "best bugcrowd program", "/pick-program". NOT for hunting a program you've already chosen (use /bug-hunt) or auditing your own app (use /security-dude or /bug-finder-dude).

  • Reads credentials

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 2 are distinctive, and 13 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 13

    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 350,495 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
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.