scope-manager
Skill1 starsChanged 3 months agoMITView on GitHub
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- agent-safetySkill
- ai-llmSkill
- apiSkill
- asset-graphSkill
- authSkill
- auto-researchSkill
- binary-analysisSkill
- business-logicSkill
- campaignSkill
- cicd-securitySkill
- cloudSkill
- cors-csrfSkill
- coverageSkill
- cross-accountSkill
- domain-modelSkill
- enrichmentSkill
- evaluation-harnessSkill
- file-uploadSkill
- graphql-auditSkill
- http-protocolSkill
- identity-domainSkill
- impact-verifierSkill
- meme-coin-auditSkill
- mobileSkill
- modern-browserSkill
- nuclei-scannerSkill
- oob-infraSkill
- osintSkill
- personaSkill
- plannerSkill
- privescSkill
- program-memorySkill
- race-conditionSkill
- rceSkill
- reconSkill
- reportingSkill
- sastSkill
- skill-scientistSkill
- sqliSkill
- ssrfSkill
- standard-catalogSkill
- technique-kbSkill
- traffic-corpusSkill
- triage-validationSkill
- vuln-intelSkill
- web3-auditSkill
- xssSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 70
Add the scope evidence directory to .gitignore so snapshots stay out of the repository, and redact (sanitize) any auth header, token, or …
- Very specific: line 77
Use guard-request before api, xss, sqli workflows to prevent OOS testing
- Very specific: line 78
Use track-scope after bb-init to establish baseline
- Very specific: line 79
Use check-changes before each session to detect program scope updates
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Scope Manager
Overview
Structured scope definition, validation, versioning, and guardrails for bug bounty engagements. Prevents accidental out-of-scope testing and tracks scope evolution over time.
Quick Reference
- Skill: scope-manager
- Version: 1.0.0
- Bounded Context: ScopeManagementContext
- Required tools:
python3 - Risk tier: passive (read-only, no target interaction)
Available Workflows
| Workflow | Purpose | Safety Tier |
init-scope | Generate structured scope file for new target | passive |
validate-url | Check if URL is within scope | passive |
diff-scope | Compare two scope files | passive |
guard-request | Guard HTTP request against scope | passive |
track-scope | Save scope snapshot for versioning | passive |
check-changes | Detect scope changes since last snapshot | passive |
export-scope | Export scope in JSON or text format | passive |
Workflow Selection
| Intent | Workflow |
| Create initial scope file | init-scope |
| Check if URL is in scope | validate-url |
| Compare two scope files | diff-scope |
| Guard a request before sending | guard-request |
| Save scope snapshot | track-scope |
| Detect scope changes | check-changes |
| Export scope data | export-scope |
Scope File Format
# In Scope
example.com
*.example.com
api.example.com
# Out of Scope
www.example.com/blog
mail.example.com
# APIs
api.example.com/v1
api.example.com/v2
# Mobile Apps
# iOS: com.example.app
# Android: com.example.appEvidence Required
For every scope operation, collect:
- Scope file content and SHA-256 hash
- Timestamp of creation/modification
- Program name and target domain
- Diff output when comparing versions (added/removed items)
- Guard decision log (URL, allowed/disallowed, reason)
- Validation results for batch URL checks
Data Handling and Safety
Scope files, guard decision logs, and any captured auth headers, session
identifiers, tokens, or cookies are kept local-only and are never committed.
Add the scope evidence directory to .gitignore so snapshots stay out of the
repository, and redact (sanitize) any auth header, token, or cookie value
before including request samples in an exported report or shared evidence
bundle. All scope-manager workflows are passive and read-only — they perform no
target interaction beyond inspecting URLs against the local scope file.
Integration with Other Skills
- Use
guard-requestbeforeapi,xss,sqliworkflows to prevent OOS testing - Use
track-scopeafterbb-initto establish baseline - Use
check-changesbefore each session to detect program scope updates
References
- OWASP WSTG-INFO-01 (Conduct Search Engine Discovery)
- HackerOne Scope Best Practices
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

