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.
git clone --depth 1 https://github.com/ogrodev/fsocietyWrote 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/payload)<a href="https://agentmods.dev/commands/ogrodev/fsociety/payload"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/payload/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/payload"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/payload.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.00019 | $0.00543 |
| Opus 5.5 | $0.00008 | $0.00217 |
| Sonnet 5.5 | $0.00004 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
payload 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.
Payload Generation
Type: $1
Context: $2
Generate targeted security testing payloads using Hexstrike AI tools.
Step 1: Load Tools
Use ToolSearch to load:
ai_generate_payload— contextual payload generationai_test_payload— payload testing and validationai_generate_attack_suite— comprehensive attack suite generationadvanced_payload_generation— payloads with WAF evasion techniques
Step 2: Identify Payload Type
Map the requested type to the appropriate category:
- xss — Cross-site scripting (reflected, stored, DOM)
- sqli — SQL injection (union, blind, time-based, error-based)
- lfi — Local file inclusion / path traversal
- rfi — Remote file inclusion
- cmdi — Command injection (Unix, Windows)
- ssrf — Server-side request forgery
- ssti — Server-side template injection
- xxe — XML external entity injection
- nosqli — NoSQL injection (MongoDB, etc.)
Step 3: Generate Payloads
Run ai_generate_payload with:
- The vulnerability type from step 2
- Target context (URL, parameter, technology stack, WAF type)
- Request WAF-evasion variants if a WAF is known
Step 4: Generate Attack Suite
If a broader test is needed, run ai_generate_attack_suite to create a comprehensive set of payloads covering multiple injection points and evasion techniques.
Step 5: Advanced Evasion
If the target is WAF-protected, also run advanced_payload_generation with evasion context for:
- Encoding variations (URL, double-URL, Unicode, hex)
- Case manipulation
- Comment insertion
- Whitespace alternatives
- Concatenation techniques
Step 6: Test Payloads
Optionally run ai_test_payload against the target to validate which payloads succeed and which are blocked.
Step 7: Output
Present payloads organized by:
- Clean payloads — no evasion, for testing without WAF
- WAF bypass payloads — evasion techniques applied
- Blind/out-of-band payloads — for targets with no visible response
Include usage instructions for each payload (where to inject, expected response).
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 · 19 tokens per session scan A fe537e21a64e
payload is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 19 tokens to every session and 543 once invoked, about $0.0001 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.