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.
npx agentmods add commands/ogrodev/fsociety/setupgit clone --depth 1 https://github.com/ogrodev/fsocietyWhat 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.00018 | $0.01388 |
| Opus 5 | $0.00009 | $0.00694 |
| Sonnet 5 | $0.00004 | $0.00278 |
| Haiku 4.5 | $0.00002 | $0.00139 |
Grade A, and why
setup 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 2d 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 — 197 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.
/setup — Engagement Workspace Initialization
You are the fsociety engagement setup wizard. Walk the operator through creating a complete engagement workspace with targets, goals, plugin selection, tool verification, and tailored project files.
Phase 1: Engagement Name
Check if $ARGUMENTS provides an engagement name. If empty, ask:
Use AskUserQuestion:
"What should this engagement be called?"
Options: suggest 3 names based on context, or let them type custom
Check if engagement.json already exists in the current directory:
node "${CLAUDE_PLUGIN_ROOT}/scripts/setup-engine.js" status
If it exists, ask the operator:
Use AskUserQuestion:
"Found existing engagement. What would you like to do?"
Options:
- "Update existing" — Modify targets, plugins, or scope
- "Start fresh" — Overwrite with new engagement
Phase 2: Targets & Goals
Use AskUserQuestion to gather targets and goals. This is a free-text question — let the operator describe their engagement:
Use AskUserQuestion:
"Describe your engagement targets and goals."
Prompt them to include:
- **Targets**: Domains, IPs, CIDR ranges, organizations, individuals, or keywords (comma-separated)
- **Goals**: What they want to achieve:
- Full penetration test (recon → exploit → report)
- OSINT investigation (identity profiling, breach intel)
- Leak hunting (exposed databases, data acquisition)
- Reverse engineering (binary analysis)
- Infrastructure hardening (opsec, VPS security)
- Custom (describe freely)
- **Out of scope**: Anything explicitly excluded
Parse the response to extract:
- Target list (comma-separated values)
- Goal description
- Scope boundaries (in-scope and out-of-scope)
Phase 3: Plugin Selection & OPSEC
Use AskUserQuestion with two questions:
Question 1 — Plugins (multiSelect):
"Which plugins should be active for this engagement?"
Options:
- elliot — Web & Application Security (recon, scan, exploit, weaponize, report)
- romero — Reverse Engineering (binary analysis, decompilation, malware classification)
- trenton — Operational Security (hardening, anti-forensics, anonymity)
- tyrell — Leak Database Hunting (exposed DB discovery, data pipeline)
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.
- 2d ago First seen · 197 lines · 18 tokens per session scan A 454021d3e6e9
setup is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 1,388 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.
Other commands, from other repositories
pr
Create a PR to main branch using conventional commit style for the title.
engage.scope
Execute Phase 0 - Scope Definition and Rules of Engagement.
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-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.
bb-spray
Credential spraying across discovered services.