security-bounty-hunter

Identify exploitable security issues in repositories for bounty submissions.

2|Updated Mar 3, 2026

Search Tags:#security #vulnerability #reporting #triage #poc #bug-bounty #bounty

Ready to run

npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill security-bounty-hunter-momodaviluke

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-bounty-hunter
Source: https://github.com/MomoDaviluke/star-citizen-promotion/tree/main/.agents/skills/ecc/security-bounty-hunter
Command: npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill security-bounty-hunter-momodaviluke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vulnerability researchers and security teams struggle to identify and prioritize real, bounty-worthy issues in repositories for responsible disclosure.

Core Features & Use Cases

Focus on remotely reachable, user-controlled attack paths and systematic triage to filter out noise.
Provides a structured workflow to generate reproducible PoCs, scope checks, and clear reports for submission to bounty programs.
Ideal for security researchers performing quick triage, in-depth audits of codepaths, or preparing a formal vulnerability submission.

Quick Start

Analyze a target repository to surface exploitable paths and prepare a bounty-ready report.

Frequently Asked Questions about security-bounty-hunter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify exploitable vulnerabilities in a codebase for a bug bounty submission?▼

To identify exploitable vulnerabilities for bug bounty submissions, analyze target repositories for remotely accessible attack paths, misconfigurations, and input handling flaws. This involves systematic triage to filter noise and focus on real-world risk findings suitable for responsible disclosure.

How do I create a reproducible proof of concept for security vulnerabilities?▼

Creating a reproducible proof of concept (PoC) involves generating structured reports that detail the exploitable security issue, scope checks, and clear documentation. This workflow ensures your vulnerability submission includes practical triage criteria and reproducible evidence for bounty programs.

What is vulnerability triage and how does it filter out noise in security reporting?▼

Vulnerability triage is the systematic process of evaluating codepaths to filter out non-exploitable noise and prioritize real, bounty-worthy issues. It focuses on remotely reachable, user-controlled attack paths to ensure findings represent genuine security risks.

Can I use automated vulnerability reporting for responsible disclosure across different platforms?▼

Yes, you can apply automated vulnerability reporting across codebases on various platforms. It systematically checks scope, applies triage criteria, and generates structured reporting templates to support responsible disclosure and bounty submissions regardless of the underlying platform.

What is the best way to prepare a formal vulnerability submission for a bounty program?▼

The best way to prepare a formal vulnerability submission is to generate a bounty-ready report containing scope checks, reproducible PoCs, and structured findings. This ensures your submission meets the practical triage and reporting requirements of bounty programs.

Why focus on remotely accessible attack paths during a repository security audit?▼

Focusing on remotely accessible attack paths during a security audit prioritizes user-controlled entry points that pose real-world risks. This approach ensures discovered vulnerabilities are exploitable and relevant for bounty submissions rather than theoretical issues.