Automate validated bug bounty finding submission as HackerOne H1 reports via API.
npx skills add https://github.com/AshtonVaughan/bountyhound --skill h1-submit
Please help me install this Agent Skill. Skill: h1-submit Source: https://github.com/AshtonVaughan/bountyhound/tree/main/bountyhound/skills/h1-submit Command: npx skills add https://github.com/AshtonVaughan/bountyhound --skill h1-submit
HackerOne report submission flows can be tedious and error-prone. This skill automates turning a validated bug bounty finding into an H1 report via the HackerOne API, reducing manual steps and ensuring consistent formatting and evidence handling.
Provide the program handle and the prepared finding-draft JSON, then submit to the H1 API.
High-intent search queries and answers about installing and using this skill.
Automating HackerOne bug bounty report submission involves using the H1 API to submit a prepared finding-draft JSON. This workflow handles credential setup, dedup checks, scope resolution, evidence attachment, and final report submission.
A finding-draft JSON is a properly formed data structure containing validated bug bounty details. It is required for H1 report submission because it enforces program-record synchronization and ensures consistent formatting before sending the report to the HackerOne API.
Yes, you can check for duplicate HackerOne reports before submitting. The submission workflow includes integrated dedup checks and program gating to reduce false positives and prevent submitting duplicate findings via the API.
Attaching evidence to a bug bounty report using the HackerOne API is handled automatically during the submission workflow. The process drafts finding details, attaches evidence files, and records results for an audit trail before final submission.
Yes, automated H1 report submission handles program scope resolution. The workflow includes scope resolution and program gating steps to ensure the validated finding falls within the target program's defined scope before final API submission.
HackerOne API report submission fails during program-record synchronization if the finding-draft JSON is improperly formed or if the program record is not correctly synchronized. Ensuring a properly structured draft and valid program handle prevents these submission errors.
chrismcmackenTriage artifact scan results to surface reportable bug bounty findings.
dreadnodeClassify bug bounty findings into eligibility tiers and generate impact justification blocks.
mikersaysUpdate planning items by ID or title with status, priority, dates, and notes.
Kilo-OrgUpscale and sharpen images while reducing artifacts for digital assets.
