/dirscan

description: Directory and content discovery with recursive crawling
allowed-tools: ToolSearch, Bash, Read, Write
argument-hint: <target-url>

> **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 discovery
• `gobuster_scan` — fast directory brute forcing
• `katana_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.