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 skills/ogrodev/fsociety/engagement-setupnpx skills add ogrodev/fsociety --skill engagement-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.00102 | $0.00730 |
| Opus 5 | $0.00051 | $0.00365 |
| Sonnet 5 | $0.00020 | $0.00146 |
| Haiku 4.5 | $0.00010 | $0.00073 |
Grade A, and why
engagement-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 3d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engagement Setup
Initialize a new engagement workspace with target configuration, plugin selection, tool verification, and tailored project files.
Quick Start
Run /setup to start the interactive wizard, or /setup <engagement-name> to skip the name prompt.
What Gets Created
| File | Purpose |
|---|---|
engagement.json |
Central engagement config — name, targets, plugins, opsec profile, timestamps |
CLAUDE.md |
Tailored guidance for this engagement — active plugins, commands, workflows |
README.md |
Human-readable engagement overview and status tracker |
scope.md |
Formal scope definition — in-scope, out-of-scope, rules of engagement |
targets.jsonl |
Structured target list with types (domain, ip, cidr, org, individual) |
.gitignore |
Runtime data file ignore patterns for all active plugins |
Plugin-Aware Setup
The setup process knows about all fsociety plugins and will:
- Check tool dependencies — Runs each plugin's tool-checker (Tier 1/2/3)
- Tailor CLAUDE.md — Only includes commands and skills for active plugins
- Configure OPSEC profiles — Maps unified profile (surface/standard/paranoid) to each plugin's native profiles
- Detect cross-plugin pipelines — Documents tyrell→elliot data flows when both are active
- Generate goal-specific workflows — Suggests first commands based on engagement goals
Available Plugins
| Plugin | Domain | Agents |
|---|---|---|
| elliot | Web & Application Security | scout, darlene |
| romero | Reverse Engineering | cipher |
| trenton | Operational Security | ghost, cleaner |
| tyrell | Leak Database Hunting | joanna, scott |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 70 lines · 102 tokens per session scan A 4b6dbc0e2b9b
engagement-setup is a skill published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 102 tokens to every session and 730 once invoked, about $0.0005 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 skills, from other repositories
pwnote-engagement-file
Create or validate a pwnote engagement import/export JSON file. Use when the user wants to generate, edit, or verify a pwnote engagement file for data transfer between pwnote instances. The file bundles an entire pentest engagement — metadata, notebook documents, code/host/credential blocks, findings with…
pwnote-cve-research
Use whenever the user is doing vulnerability research aimed at a CVE/advisory — tracking a responsible disclosure timeline, drafting a vendor notification, requesting a CVE ID from MITRE or a CNA, writing a public security advisory, or mapping a finding to a CWE. Trigger on "CVE", "CNA", "MITRE", "advisory"…
pwnote-offsec-osai
Use whenever the user is working on Offsec's OSAI / AI Red Teaming certification track, or on AI/LLM/agentic security engagements generally — prompt injection findings, tool-use abuse, agent trajectory documentation, or writing up AI-specific security findings that don't map cleanly to traditional CVSS. Trigger on…
pwnote-offsec-web300
Use whenever the user is working on Offsec's WEB-300 course/OSWE — whitebox source code review methodology, exploit chain documentation, PoC scripting, or OSWE exam report writing. Trigger on "OSWE", "WEB-300", "whitebox", "source code review" in a pentest context, or "exploit chain", even without the word "skill".
pwnote-hackthebox
Use whenever the user is working a HackTheBox (HTB) machine or challenge — structuring recon/foothold/privesc notes, building an enumeration checklist, tracking a multi-hop attack path, or writing a writeup (respecting HTB's retirement rules before publishing). Trigger on "HTB", "HackTheBox box", "pwn this machine"…
pwnote-offsec-pen200
Use whenever the user is working on Offsec's PEN-200 course/OSCP — PWK lab notes, exam report drafting, screenshot/evidence discipline, or exam flag handling. Trigger on "OSCP", "PEN-200", "PWK", "OSCP exam report", or "proof.txt", even without the word "skill".