A command that sets the authorized target for web testing and identifies its technologies, such as its framework, programming language, server, and web firewall.

Use it at the start of a web security engagement to define domains and subdomains, choose a scan profile, and detect the target’s technology stack.

It keeps testing focused on approved hosts and gives you an initial picture of how the target is built.

scope — Command by ogrodev

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/ogrodev/fsociety/scope

Clone the repo

git clone --depth 1 https://github.com/ogrodev/fsociety

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 571 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00010	$0.00571
Opus 5	$0.00005	$0.00285
Sonnet 5	$0.00002	$0.00114
Haiku 4.5	$0.00001	$0.00057

Measured yesterday against content hash 54e6d27a78ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

scope scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

elliot/commands/scope.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Storage Policy: ALL output files MUST be saved in the project directory. NEVER write to /tmp/ or any system temporary directory.

Set Engagement Scope

Target and options: $ARGUMENTS

Configure the engagement scope and perform initial target profiling.

Step 0: Parse Profile Flag

If $ARGUMENTS contains --profile <name>, extract the profile and set it:

node "${CLAUDE_PLUGIN_ROOT}/scripts/scan-profile.js" set <profile>

The remaining argument (without --profile) is the target domain.

Step 1: Load Tools

Use ToolSearch to load:

http_set_scope — define in-scope hosts for HTTP testing tools
detect_technologies_ai — AI-powered technology detection
wafw00f_scan — WAF detection

Step 2: Set HTTP Scope

Run http_set_scope to register the target domain (and any known subdomains) as in-scope. This configures the HTTP testing framework tools (repeater, intruder) to only operate within authorized targets.

Step 3: Technology Detection

Run detect_technologies_ai on the target to identify:

CMS / Framework (WordPress, React, NestJS, etc.)
Programming languages
Web servers
JavaScript libraries
CDN / WAF / reverse proxy

Step 4: WAF Fingerprinting

Run wafw00f_scan to identify specific WAF products. This is critical for selecting appropriate evasion techniques in later testing.

Step 5: Create Scope Document

Write a scope.md file in the project directory with:

Target domain and in-scope subdomains
Technology stack detected
WAF/CDN information
Testing constraints (rate limits, restricted hours, etc.)
Recommended tool configurations based on detected defenses

Step 6: Auto-Log Intel

If target-intel.js exists, log discovered tech stack and defenses:

# For each technology detected:
node "${CLAUDE_PLUGIN_ROOT}/scripts/target-intel.js" add "<target>" "tech-stack" "<tech-name>" "<version-or-details>" --source scan
# For WAF/CDN detected:
node "${CLAUDE_PLUGIN_ROOT}/scripts/target-intel.js" add "<target>" "defense" "<defense-name>" "<details>" --source scan

Read the full file on GitHub · 60 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 60 lines · 10 tokens per session scan A 54e6d27a78ad

Subscribe to this mod's changes

scope is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 571 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Security Testing claude-code claude-code-plugin offensive-security pentesting

pr

Create a PR to main branch using conventional commit style for the title.

KeygraphHQ/shannon · 13 tokens

engage.scope

Execute Phase 0 - Scope Definition and Rules of Engagement.

hypnguyen1209/offensive-claude · 11 tokens

pentest

Activate pentest mode — displays ASCII art, configures session isolation, collects engagement scope, then OWNS the engagement: pre-flight, recon, planning (via the pentester-orchestrator planner), executor dispatch, a time-budget quota loop, aggregation, and report generation.

Stickman230/claude-pentest · 58 tokens

scope