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/dirscan)<a href="https://agentmods.dev/commands/ogrodev/fsociety/dirscan"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/dirscan/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/dirscan"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/dirscan.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.00007 | $0.00429 |
| Opus 5.5 | $0.00003 | $0.00172 |
| Sonnet 5.5 | $0.00001 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
dirscan 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.
Directory & Content Discovery
Target: $ARGUMENTS
Execute comprehensive directory and content discovery using Hexstrike MCP tools.
Step 1: Load Tools
Use ToolSearch to load:
feroxbuster_scan— recursive content discoverygobuster_scan— fast directory brute forcingkatana_crawl— intelligent web crawling with JS rendering
Step 2: Feroxbuster (Primary)
Run feroxbuster_scan against the target with:
- Recursive discovery enabled
- Common extensions based on target tech stack (php, js, html, json, txt, bak, old, conf)
- Appropriate wordlist (common.txt or directory-list-2.3-medium.txt)
- Status code filtering: include 200, 301, 302, 403 (403 can reveal protected paths)
- Rate limiting for WAF-protected targets
Step 3: Gobuster (Supplementary)
Run gobuster_scan in directory mode with a different wordlist than feroxbuster to maximize coverage. Include vhost mode if subdomain enumeration is relevant.
Step 4: Katana Crawl
Run katana_crawl for JavaScript-aware crawling that discovers dynamically generated paths, API endpoints in client-side code, and linked resources that brute-forcing misses.
Step 5: Results
Deduplicate findings across all tools. Present organized by:
- Interesting files: config files, backups, source code, admin panels
- API endpoints: discovered REST/GraphQL paths
- Protected paths: 401/403 responses that may be accessible with auth
- Redirects: 301/302 that reveal application structure
Save to dirscan-{target}.md in the project directory.
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 · 43 lines · 7 tokens per session scan A e7d072d0b785
dirscan is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 429 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.