hackerone

Parse HackerOne scope CSV exports and generate submission-ready markdown reports.

Updated May 27, 2026
One-click install
npx skills add https://github.com/hoanghn61/.agents --skill hackerone-hoanghn61
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hackerone
Source: https://github.com/hoanghn61/.agents/tree/main/skills/hackerone
Command: npx skills add https://github.com/hoanghn61/.agents --skill hackerone-hoanghn61

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It reduces the time and effort required to prepare high-quality HackerOne submissions by automating program scope processing, parallel testing, proof-of-concept validation, and report formatting.

Core Features & Use Cases

  • Program Analysis & Scope Parsing: Parse HackerOne scope CSV exports and filter to eligible assets for submission.
  • Automated Parallel Testing: Orchestrate pentesting across many assets concurrently using an agent-based workflow.
  • PoC Validation & Evidence Packaging: Ensure every finding includes executable PoC outputs and supporting evidence references to reduce rejection risk.
  • HackerOne-Ready Report Generation: Produce submission-ready markdown reports with required sections like reproduction steps, impact, and remediation guidance.

Quick Start

Run the command "/hackerone https://hackerone.com/example-corp" to fetch program policy, download the scope CSV, test eligible assets in parallel, validate PoCs, and generate HackerOne-ready submissions.

Frequently Asked Questions about hackerone

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

FAQPage Schema
How do I automate HackerOne bug bounty report generation from a program scope?

You can automate report generation by starting from a HackerOne program URL or scope CSV file, running parallel vulnerability testing on eligible assets, and producing submission-ready markdown reports with validated PoC evidence and required severity sections.

What is parallel pentesting and how does it apply to HackerOne scope parsing?

Parallel pentesting orchestrates agent-based vulnerability testing across many eligible assets concurrently. It applies to HackerOne scope parsing by taking filtered assets from a scope CSV export and testing them simultaneously to identify findings efficiently.

How do I validate PoC artifacts for HackerOne security submissions?

Validating PoC artifacts for HackerOne security submissions requires ensuring every finding includes executable proof-of-concept outputs and supporting evidence references. This validation reduces rejection risk by confirming reproducibility before generating the final markdown report.

Can I use a manually provided asset list instead of a HackerOne scope CSV export?

Yes, the workflow accepts a manually provided asset list as an alternative to a HackerOne scope CSV export. It supports three input types: a HackerOne program URL, a downloaded scope CSV file, or a manually provided asset list targeting specific guideline sets.

What sections are required in a HackerOne-compliant submission markdown report?

A HackerOne-compliant submission markdown report must include sections for reproduction steps, impact analysis, and remediation guidance. It also requires severity and CVSS content, along with executable PoC outputs and evidence references to validate findings.

Does parallel pentesting work with specific HackerOne guideline sets?

Yes, parallel pentesting applies to scenarios where testers target specific HackerOne guideline sets. The workflow parses program scope exports and deploys parallel vulnerability testing per eligible asset based on those targeted guidelines.