agentleFS
zyphr-labszyphr-labs/bounty-harness/.claude/skills/scope-manager/SKILL.md

scope-manager

Skill1 starsChanged 3 months agoMITView on GitHub

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
  1. Very specific:

    Add the scope evidence directory to .gitignore so snapshots stay out of the repository, and redact (sanitize) any auth header, token, or …

    line 70
  2. Very specific:

    Use guard-request before api, xss, sqli workflows to prevent OOS testing

    line 77
  3. Very specific:

    Use track-scope after bb-init to establish baseline

    line 78
  4. Very specific:

    Use check-changes before each session to detect program scope updates

    line 79

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

WorkflowPurposeSafety Tier
init-scopeGenerate structured scope file for new targetpassive
validate-urlCheck if URL is within scopepassive
diff-scopeCompare two scope filespassive
guard-requestGuard HTTP request against scopepassive
track-scopeSave scope snapshot for versioningpassive
check-changesDetect scope changes since last snapshotpassive
export-scopeExport scope in JSON or text formatpassive

Workflow Selection

IntentWorkflow
Create initial scope fileinit-scope
Check if URL is in scopevalidate-url
Compare two scope filesdiff-scope
Guard a request before sendingguard-request
Save scope snapshottrack-scope
Detect scope changescheck-changes
Export scope dataexport-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.app

Evidence 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-request before api, xss, sqli workflows to prevent OOS testing
  • Use track-scope after bb-init to establish baseline
  • Use check-changes before each session to detect program scope updates

References

  • OWASP WSTG-INFO-01 (Conduct Search Engine Discovery)
  • HackerOne Scope Best Practices

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.