Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ogrodev/fsociety/plugin install elliotWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/ogrodev/fsociety/scope)<a href="https://agentmods.dev/commands/ogrodev/fsociety/scope"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/scope/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ogrodev/fsociety/scope"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/scope.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00010 | $0.00571 |
| Opus 5.5 | $0.00004 | $0.00228 |
| Sonnet 5.5 | $0.00002 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
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 2mo ago.
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.
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 toolsdetect_technologies_ai— AI-powered technology detectionwafw00f_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
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.
- 2mo ago First seen · 60 lines · 10 tokens per session scan A 54e6d27a78ad
scope is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 571 once invoked, about $0.0000 per session on Opus 5.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.
Other commands, from other repositories
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.
pentest-scope
Define or update engagement scope — saves scope to disk without launching a pentest. Can be run before or during an engagement. If a pentest is active and the target changes drastically, warns the operator and suggests a new engagement.
pentest-attacks
Define the attack profile for an engagement — select which attack categories and skills to use. Saves to .pentest-attacks.json. If run before /pentest:pentest, the orchestrator will respect the selection. If run standalone, does not launch a pentest.
pentest-kali
Connect to a Metasploit-Kali Server (MKS) REST API — verifies connectivity, discovers available Kali tools, and configures agents to prefer MKS endpoints over local Bash equivalents.
pentest-exit
Close pentest session — summarizes findings, ensures outputs are saved, lifts isolation, and prompts for /clear.
bb-ad
Active Directory enumeration and attack techniques. Includes LDAP enumeration, Kerberos attacks (Kerberoasting, AS-REP Roasting), SMB attacks, and domain privilege escalation. Use this when targeting Windows domain environments.