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/report)<a href="https://agentmods.dev/commands/ogrodev/fsociety/report"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/report/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/report"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/report.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.00008 | $0.00382 |
| Opus 5.5 | $0.00003 | $0.00153 |
| Sonnet 5.5 | $0.00002 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
report 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.
What it actually says
Storage Policy: ALL output files MUST be saved in the project directory. NEVER write to
/tmp/or any system temporary directory.
Generate Vulnerability Report
Generate a comprehensive penetration test report from findings in the current engagement.
Step 1: Load Tools
Use ToolSearch to load:
create_vulnerability_report— formatted vulnerability report generationcreate_scan_summary— scan result summarization
Step 2: Gather Findings
Read all reconnaissance and scan output files in the project directory:
- Use Glob to find
*.mdfiles in the current directory and subdirectories - Look for ATTACK-VECTORS.md, VULNERABILITY-REPORT.md, or similar
- Read scan outputs (webscan-, apiscan-, portscan-*, etc.)
- Check
reports/subdirectory for detailed findings
Step 3: Scan Summary
Run create_scan_summary to generate a consolidated summary of all tool outputs from this engagement.
Step 4: Vulnerability Report
Run create_vulnerability_report with all discovered vulnerabilities, organized by:
- CVSS severity (Critical → Info)
- Vulnerability type (injection, auth, config, etc.)
- Each finding should include:
- Title and description
- Affected endpoint/component
- Steps to reproduce
- Evidence/proof
- Impact assessment
- Remediation recommendation
Step 5: Output
Save the report to PENTEST-REPORT-{date}.md in the project directory.
Include:
- Executive summary
- Scope and methodology
- Findings by severity
- Risk matrix
- Remediation priority list
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 · 49 lines · 8 tokens per session scan A 36280dbd719f
report is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 382 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.