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.
npx agentmods add skills/blisspixel/recon/reconnpx skills add blisspixel/recon --skill recongit clone --depth 1 https://github.com/blisspixel/reconWrote 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/skills/blisspixel/recon/recon)<a href="https://agentmods.dev/skills/blisspixel/recon/recon"><img src="https://agentmods.dev/badge/skills/blisspixel/recon/recon.svg" alt="Measured on agentmods" 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 | $0.00124 | $0.05441 |
| Opus 5 | $0.00062 | $0.02721 |
| Sonnet 5 | $0.00025 | $0.01088 |
| Haiku 4.5 | $0.00012 | $0.00544 |
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 3d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
recon
Public-metadata domain intelligence. Given an apex domain, recon returns hedged observations about that queried public namespace and its evidence-linked service and identity indicators. It uses public DNS, certificate transparency, and unauthenticated identity-discovery endpoints without credentials or API keys. Default collection performs no active scanning or port probing: authoritative DNS may observe resolver traffic, and MTA-STS is the only default target-owned HTTP/application request. Google CSE and BIMI certificate requests are explicit opt-in direct probes.
When this is the right tool
Reach for recon when the user wants to understand a domain's public-facing configuration:
- "Is
delta.invalidon Microsoft 365? What's their tenant ID?" - "Score the email security on
gamma.invalid." - "What SaaS vendors does
beta.invalidappear to use?" - "Find related domains for
alpha.invalid." - "Compare the posture of
a.invalidandb.invalid."
Do not reach for recon when the user wants:
- Active scanning, port scans, or credentialed inventory.
- Vulnerability assessment or exploit checks.
- Company financials, news, hiring signals, or firmographic data.
- Generic target-owned application crawling. The only direct target interactions are the standards-compliant
mta-sts.{domain}request on the default path and the documented CSE / BIMI certificate probes when explicitly enabled.
If the user wants a verdict like "is this company secure," recon is not that tool. It surfaces observations; the user supplies the judgment.
Before first invocation
Confirm recon is installed before the first call in a session:
recon --version
If the command is not found:
"
recon-toolis not installed. It's a Python CLI from github.com/blisspixel/recon that reads public DNS, identity endpoints, and certificate transparency - no credentials needed. Install withpip install recon-tool? (Python 3.11+ required.)"
Wait for explicit approval, then pip install recon-tool followed by recon doctor to verify connectivity. If recon --version succeeds, continue immediately - do not re-prompt on subsequent calls in the same session.
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.
- 3d ago First seen · 317 lines · 124 tokens per session scan A 161a31aaa96b
recon is a skill published in the GitHub repository blisspixel/recon (4 stars, last pushed 4d ago), licensed Apache-2.0. It adds 124 tokens to every session and 5,441 once invoked, about $0.0006 per session on Opus 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-31.
Other skills, from other repositories
github-secret-hunting
Find leaked API keys, tokens, and credentials in public GitHub repositories.
google-dorks-catalog
High-precision Google dorks for exposed configs, secrets, and credentials -- real-world validated.
metabigor
Use when operating the metabigor CLI for OSINT recon and infrastructure mapping without API keys. Covers finding network ranges from an ASN, org, domain, or IP (net); enumerating subdomains from certificate logs (cert); enriching IPs with ports/CVEs via Shodan InternetDB (ip); searching public GitHub code for secrets…
web-recon
Full offensive reconnaissance skill for Web Pentest and Bug Bounty. Activate when the user mentions recon, reconnaissance, subdomain enumeration, attack surface mapping, bug bounty recon, or any variation of "start a pentest" on a domain/target. Covers: subdomain enumeration, DNS resolution, live detection…
offensive-osint
Operational arsenal for authorized external red-team and bug-bounty recon. Concrete probes, wordlists, regexes, dorks, curl one-liners for: subdomain enum, GraphQL/Swagger/REST discovery, identity fabric (Entra/Okta/ADFS/Google/SAML/M365 deep — Teams/SharePoint/OneDrive), cloud bucket enum (S3/GCS/Azure), CDN/WAF…
osint-methodology
Comprehensive OSINT methodology for external red-team operations and authorized attack-surface assessments. Covers the 5-stage recon pipeline (seed discovery, asset expansion, enrichment, exposure analysis, reporting), asset-graph discipline with 29 asset types, severity rubric (CRITICAL/HIGH/MEDIUM/LOW/INFO)…