Skip to main content
Agent skill

Security Bounty Hunter

Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings. Use when hunting reportable, remotely reachable vulnerabilities in a repository.

Get started

Get the complete skill folder, including its scripts and reference files.

·

When to use this skill

Use Security Bounty Hunter when an AI agent needs a reusable SKILL.md workflow for this job: Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings. Use when hunting reportable, remotely reachable vulnerabilities in a repository.

When not to use it

Skip Security Bounty Hunter when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/security-bounty-hunter
# Save SKILL.md to ~/.claude/skills/security-bounty-hunter/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/security-bounty-hunter/SKILL.md. For a shared project, commit the folder at .claude/skills/security-bounty-hunter/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Security Bounty Hunter skill for this task: Scanning a repository for exploitable vulnerabilities. Confirm any required inputs or files before making changes.

What supports this recommendation?

83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
92/100
Practical detail
92/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Security Bounty Hunter

Use this when the goal is practical vulnerability discovery for responsible disclosure or bounty submission, not a broad best-practices review.

## When to Use

- Scanning a repository for exploitable vulnerabilities - Preparing a Huntr, HackerOne, or similar bounty submission - Triage where the question is "does this actually pay?" rather than "is this theoretically unsafe?"

## How It Works

Bias toward remotely reachable, user-controlled attack paths and throw away patterns that platforms routinely reject as informative or out of scope.

## In-Scope Patterns

These are the kinds of issues that consistently matter:

| Pattern | CWE | Typical impact | | --- | --- | --- | | SSRF through user-controlled URLs | CWE-918 | internal network access, cloud metadata theft | | Auth bypass in middleware or API guards | CWE-287 | unauthorized account or data access | | Remote deserialization or upload-to-RCE paths | CWE-502 | code execution | | SQL injection in reachable endpoints | CWE-89 | data exfiltration, auth bypass, data destruction | | Command injection in request handlers | CWE-78 | code execution | | Path traversal in file-serving paths | CWE-22 | arbitrary file read or write | | Auto-triggered XSS | CWE-79 | session theft, admin compromise |

## Skip These

These are usually low-signal or out of bounty scope unless the program says otherwise:

- Local-only `pickle.loads`, `torch.load`, or equivalent with no remote path - `eval()` or `exec()` in CLI-only tooling - `shell=True` on fully hardcoded commands - Missing security headers by themselves - Generic rate-limiting complaints without exploit impact - Self-XSS requiring the victim to paste code manually - CI/CD injection that is not part of the target program scope - Demo, example, or test-only code

## Workflow

1. Check scope first: program rules, SECURITY.md, disclosure channel, and exclusions. 2. Find real entrypoints: HTTP handlers, uploads, background jobs, webhooks, parsers, and integration endpoints. 3. Run static tooling where it helps, but treat it as triage input only. 4. Read the real code path end to end. 5. Prove user control reaches a meaningful sink. 6. Confirm exploitability and impact with the smallest safe PoC possible. 7. Check for duplicates before drafting a report.

## Example Triage Loop

```bash semgrep --config=auto --severity=ERROR --severity=WARNING --json ```

Then manually filter:

- drop tests, demos, fixtures, vendored code - drop local-only or non-reachable paths - keep only findings with a clear network or user-controlled route

## Report Structure

```markdown ## Description [What the vulnerability is and why it matters]

## Vulnerable Code [File path, line range, and a small snippet]

## Proof of Concept [Minimal working request or script]

## Impact [What the attacker can achieve]

## Affected Version [Version, commit, or deployment target tested] ```

## Quality Gate

Before submitting:

- The code path is reachable from a real user or network boundary - The input is genuinely user-controlled - The sink is meaningful and exploitable - The PoC works - The issue is not already covered by an advisory, CVE, or open ticket - The target is actually in scope for the bounty program

Intended uses

  • Scanning a repository for exploitable vulnerabilities
  • Preparing a Huntr, HackerOne, or similar bounty submission
  • Triage where the question is "does this actually pay?" rather than "is this theoretically unsafe?"
  • Check scope first: program rules, SECURITY.md, disclosure channel, and exclusions.
  • Find real entrypoints: HTTP handlers, uploads, background jobs, webhooks, parsers, and integration endpoints.
  • Run static tooling where it helps, but treat it as triage input only.
  • Read the real code path end to end.
  • Prove user control reaches a meaningful sink.
  • Confirm exploitability and impact with the smallest safe PoC possible.
  • Check for duplicates before drafting a report.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.