A command for running a broad reconnaissance workflow against a domain. Reconnaissance means collecting information such as subdomains, live services, technologies, web paths, historical URLs, and open ports.

Use it to discover subdomains, probe live hosts, identify technologies and WAF protection, crawl websites, find archived URLs, and scan ports.

It gathers several types of target information in one defined sequence before later security testing.

recon — Command for Claude Code by ogrodev/fsociety

Install

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.

Clone the repo

git clone --depth 1 https://github.com/ogrodev/fsociety

Made for: Claude Code.

Or install elliot, the plugin that ships this one along with the rest of its 9 skills, 24 commands, 2 agents, 4 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ogrodev/fsociety/recon/github.svg)](https://agentmods.dev/commands/ogrodev/fsociety/recon)

Your own site

<a href="https://agentmods.dev/commands/ogrodev/fsociety/recon"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/recon/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ogrodev/fsociety/recon"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/recon.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 530 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00017	$0.00530
Opus 5.5	$0.00007	$0.00212
Sonnet 5.5	$0.00003	$0.00106
Haiku 4.5	$0.00002	$0.00053

Measured 2mo ago against content hash fcffca76eec8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

recon 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.

elliot/commands/recon.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Storage Policy: ALL output files MUST be saved in the project directory. NEVER write to /tmp/ or any system temporary directory.

Reconnaissance Workflow

Target: $ARGUMENTS

Execute a comprehensive reconnaissance workflow against the target using Hexstrike MCP tools. Follow this sequence:

Step 1: Load Tools

Use ToolSearch to load these Hexstrike tools:

subfinder_scan — passive subdomain enumeration
httpx_probe — HTTP probing and tech detection
wafw00f_scan — WAF detection and fingerprinting
detect_technologies_ai — AI-powered technology identification
katana_crawl — web crawling for endpoint discovery
gau_discovery — historical URL discovery from archives
nmap_scan — port scanning for initial service identification

Step 2: Subdomain Enumeration

Run subfinder_scan against the target domain to discover subdomains. Then probe discovered subdomains with httpx_probe to identify live hosts and their technologies.

Step 3: WAF Detection

Run wafw00f_scan on each live subdomain to identify WAF/CDN protection. This is critical for later attack planning — tools and payloads must be selected based on WAF type.

Step 4: Technology Detection

Run detect_technologies_ai on the main target and key subdomains. This identifies the full tech stack (CMS, frameworks, languages, servers) and recommends testing approaches.

Step 5: Port Scanning

Run nmap_scan against the target for a standard port scan to identify open services beyond HTTP/HTTPS.

Step 6: Crawling & URL Discovery

Run katana_crawl on the main target for deep crawling with JavaScript rendering. Also run gau_discovery to find historical URLs from web archives that may reveal hidden endpoints.

Step 7: Save Results

Save a structured reconnaissance summary to the project directory as recon-{target}.md including:

Discovered subdomains and their status
WAF/CDN information per host
Technology stack details
Open ports and services
Discovered endpoints and URLs
Recommended next steps based on findings

Read the full file on GitHub · 50 lines

Changes

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 · 50 lines · 17 tokens per session scan A fcffca76eec8

Subscribe to this mod's changes

recon is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 530 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.

Claude Code Productivity Security claude-code-plugin offensive-security pentesting

engage.actions

Execute Phase 7 - Actions on Objectives and Goal Achievement.

hypnguyen1209/offensive-claude · 11 tokens

orchestrate

Do this task as an orchestrator. The aim is the same result at a fraction of the cost: in a long session, every token in this conversation is re-read on each later request, while a subagent's reading is discarded when it returns. The plugin's subagents run on Haiku 5.5, about 40× cheaper per token than Opus 5.5.

egorfedorov/claude-context-optimizer · 0 tokens

scout-meta-review

Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.

Raven-Scout/Scout · 61 tokens

recon