Sequester-AG / bug-bounty-triage
git clone https://github.com/Sequester-AG/bug-bounty-triage.git
Agent skill for rigorous bug bounty report triage, validation, severity escalation, and submission-ready reporting.
+0
stars, 24h · #40,243
+~0
stars, 7 days · #45,138
+139
stars, 30 days · #5,438
139
★ total
20
forks · 0 open issues
Star history (as recorded here)
LicenseMIT
Created2026-10-09 (13d ago)
Last push13d ago
Watchers0
OwnerOrganization
GitHub topics
Links
README excerpt
# bug-bounty-triage `bug-bounty-triage` is an agent skill for rigorous bug bounty report triage, independent validation, impact escalation, and submission-ready reporting. It is designed to help an agent: - reproduce findings end to end when testing is authorized; - separate observed evidence from inference; - reject weak or non-actionable reports before submission; - pursue the highest defensible impact without overstating severity; and - produce concise, evidence-heavy Markdown reports for bug bounty platforms. ## Responsible use Use this skill only on systems you own or are explicitly authorized to test. Invoking the skill does not grant permission to test a target, exceed a program's scope, access unrelated data, or perform destructive actions. The skill may preserve sensitive evidence in generated reports when the user supplies it. Review generated files before sharing or committing them, and follow the applicable bug bounty program's rules. ## Installation ### Skills CLI [code] ### Codex [code] ### Agent skills directory [code] ## Supporting skills and CLIs The full live-validation workflow uses agent-browser for browser automation and agent-email-cli for disposable test inboxes. Install both agent skills: [code] The skills provide agent instructions. Install their corresponding command-line tools for live execution: [code] ## Usage Invoke the skill with a report, vulnerability description, or target and finding: [code] For live validation, provide the relevant authorization and scope. The complete workflow can use browser automation, direct HTTP requests, and disposable email accounts when those capabilities are available in the host environment. If live testing is unavailable, the skill should state what remains unverified. ## Output For a supported, submission-ready finding, the skill writes a Markdown report named from the target and vulnerability class, such as: [code] Internal triage commentary stays outside the submission file. ## Repository contents - `SKILL.md` — skill metadata, workflow, validation gates, escalation guidance, and report format - `LICENSE` — MIT License ## License MIT