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/forefy/.context/external-enumerationnpx skills add forefy/.context --skill external-enumerationgit clone --depth 1 https://github.com/forefy/.contextWrote 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/forefy/.context/external-enumeration)<a href="https://agentmods.dev/skills/forefy/.context/external-enumeration"><img src="https://agentmods.dev/badge/skills/forefy/.context/external-enumeration.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.1 | $0.00037 | $0.03409 |
| Opus 5 | $0.00018 | $0.01705 |
| Sonnet 5 | $0.00007 | $0.00682 |
| Haiku 4.5 | $0.00004 | $0.00341 |
Grade A, and why
external-enumeration scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://crt.sh/?q=%.example.com&output=json" \ How it starts
The opening of the file, as written. The whole thing — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
External Enumeration Skill
You are performing passive external reconnaissance on a target company's domain infrastructure. Goal: produce a comprehensive, structured map of all domains, subdomains, technology stack, and notable security observations - using only passive/OSINT techniques (no active exploitation).
Phase 0 - Scope Clarification
Ask the user for:
- Primary domain(s) to enumerate (e.g.
example.com) - Known subsidiaries or related companies (acquisitions, brand names, sister domains)
- Output format - markdown report to a file path?
- Depth - quick pass (passive DNS only) or deep pass (stealth browser + port scan)?
Phase 1 - Domain Ownership & Attribution
Before enumerating subdomains, confirm what domains are actually owned by the target.
1.1 WHOIS Check
whois <domain> | grep -iE 'registrar|creation|name server|registrant'
Note: Most domains use privacy protection (e.g. GoDaddy DomainsbyProxy) - registrant names will be hidden. Do NOT rely on registrant names for attribution.
1.2 Nameserver Correlation (Primary Attribution Method)
for d in domain1.com domain2.io domain3.net; do
echo -n "$d: "; dig NS $d +short | sort | tr '\n' ' '; echo
done
Identical NS pairs = same DNS account = same owner. This is the strongest passive attribution proof even when WHOIS is privacy-protected.
1.3 MX + TXT Record Cross-Reference
dig MX <domain> +short
dig TXT <domain> +short
- Shared
*.mail.protection.outlook.comMX = same Microsoft 365 tenant - TXT records reveal: Azure site verifications, Google Workspace, Atlassian, SendGrid
- Azure TXT format:
MS=ms...orazurewebsites.netsubdomain references → same Azure tenant
1.4 Similar-Name Domain Trap
Note: Always verify similar-sounding domains (e.g.
target.net,target.co) are actually owned by the target - different registrar or NS pair = likely unrelated squatter. Never assume.
Phase 2 - Multi-Source Subdomain Enumeration
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.
- 5d ago First seen · 370 lines · 37 tokens per session scan A a3c4624fb608
external-enumeration is a skill published in the GitHub repository forefy/.context (144 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 3,409 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
eresus-manual-security-audit
Elite manual security code review skill for deep, adversarial vulnerability hunting and exploit-chain discovery. Trigger when the user asks to: "do a deep security audit", "manual code review", "find exploit chains", "hunt for logic bugs", "red-team this codebase", "do an offensive security review", "review this like…
eresus-php-audit
Deep PHP-specific security audit skill covering injection, deserialization, file operations, auth bypass, POP chain discovery, and CMS-specific patterns. Trigger when auditing PHP code: "audit this PHP app", "find PHP security issues", "check Laravel/WordPress for vulnerabilities", "PHP SAST review", "check for PHP…
eresus-sast-scanner
General-purpose Static Application Security Testing (SAST) skill for code vulnerability analysis. Trigger when the user asks to: "analyze code for vulnerabilities", "review code security", "find security bugs", "do a SAST scan", "check for [vulnerability type] in code", "audit source code", or requests a security code…
eresus-python-audit
Deep Python-specific security audit skill with 50+ vulnerability class coverage across 7 categories. Trigger when auditing Python code: "audit this Python app", "find Python security issues", "check Flask/Django for vulnerabilities", "Python SAST review", "check for pickle vulnerabilities", "review this FastAPI code".…
eresus-remediator
Security remediation skill for fixing confirmed or likely SAST findings in source code. Trigger when the user asks to: "fix a vulnerability", "patch this security bug", "remediate SAST findings", "harden this endpoint", "make this auth flow safe", or wants code changes that remove a confirmed security issue while…
eresus-variant-analysis
GHSA/CVE variant analysis workflow for finding similar vulnerability patterns across a codebase. Trigger when the user asks to: "find variants of this CVE", "GHSA variant analysis", "find similar bugs", "hunt for the same pattern", "are there other places with this vulnerability?", or when a known vulnerability is…