Scope Assessment

Verifies a target repository is in-scope for its bug bounty program before analysis.

1|Updated Mar 12, 2026

Search Tags:#security #compliance #vulnerability research #bug bounty #hackerone #scope verification #bugcrowd

Ready to run

npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill scope-assessment-kaminocorp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Scope Assessment
Source: https://github.com/kaminocorp/hermes-alpha-hunter/tree/main/hunter/skills/security/scope-assessment
Command: npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill scope-assessment-kaminocorp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security researchers risk wasting effort or violating program rules when analyzing targets that are out-of-scope for a bug bounty program. This Skill enforces a mandatory scope verification gate before any code analysis begins. ## Core Features & Use Cases - Program Discovery: Locates the bounty program on HackerOne, Bugcrowd, Intigriti, or via the repository's SECURITY.md file. - Rule Extraction: Documents in-scope assets, excluded targets, accepted vulnerability types, severity thresholds, and safe harbor terms. - Decision Gate: Produces a structured SCOPE CHECK verdict (IN-SCOPE, OUT-OF-SCOPE, UNCLEAR, or NO PROGRAM) and halts the mission when the target fails verification. - Use Case: Before auditing a GitHub repository for vulnerabilities, run this Skill to confirm the repo is listed in the organization's active HackerOne program and that source code analysis is permitted. ## Quick Start Verify whether the target repository is in-scope for its bug bounty program before starting any security analysis.

Frequently Asked Questions about Scope Assessment

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

FAQPage Schema

How do I check if a target is in scope for a bug bounty program?▼

Locate the program page on HackerOne, Bugcrowd, or Intigriti, then read the scope section listing eligible assets. Confirm the specific repository is listed, source code analysis is permitted, and the program is currently active before testing.

How to find a project's bug bounty program?▼

Search for the project name plus "bug bounty program" and check platforms like HackerOne, Bugcrowd, Intigriti, and Open Bug Bounty. Also inspect the repository for SECURITY.md or .github/SECURITY.md files linking to the policy.

What happens if a target is out of scope for its bounty program?▼

The Skill writes the finding to SUMMARY.md explaining why the target is out of scope and stops the mission immediately. Testing out-of-scope assets can violate program rules and forfeit safe harbor legal protections.

Does HackerOne scope differ from Bugcrowd scope definitions?▼

Yes. HackerOne programs list eligible assets under a Scope tab with policy rules, while Bugcrowd separates Scope and Out of Scope sections explicitly. Managed HackerOne programs often impose stricter rules such as no automated scanning.

When should a security assessment stop due to scope issues?▼

Stop when the program prohibits automated scanning, the target is a dependency not listed in scope, the program is private without an invitation, or the repository belongs to a different organization than the program covers.