reconnaissance-planning SKILL.md skillA
reconnaissance-planning from dreadnode/capabilities is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dreadnode/capabilities/reconnaissance-planning@git:20260611.414f191Pins git:20260611.414f191 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dreadnode/capabilities
- Path
capabilities/attack-surface-management/skills/reconnaissance-planning/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260611.414f191, committed Jun 11, 2026
- Size
- 4,195 bytes
- Repository stars
- 22
- License
- MIT
Strategic reconnaissance planning for external attack surface management. Use when starting a new engagement, choosing initial scan strategy, or deciding how to expand coverage after initial results.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Reconnaissance Planning ## When to Use - Starting a new ASM engagement against a target - Deciding scan strategy after initial enumeration - Expanding coverage when initial results are sparse - Pivoting approach based on discovered infrastructure ## Phased Approach ### Phase 1: Passive Discovery (Low Noise) Start with passive techniques to map the target without generating traffic. **Subdomain Enumeration:** ``` run_bbot_scan(targets=["target.com"], presets=["subdomain-enum"], flags=["passive"]) ``` This queries certificate transparency logs, DNS databases, archive.org, and OSINT sources without touching the target directly. **What to look for after Phase 1:** - Total number of discovered subdomains (establishes scale) - Naming conventions (numbered patterns like `app01`, `srv02` suggest more exist) - Cloud providers visible in DNS (CNAME to AWS, Azure, GCP) - Mail infrastructure (MX records, SPF/DKIM) - Development/staging indicators in subdomain names ### Phase 2: Active Enumeration (Moderate Noise) Probe discovered assets to understand what's running. **Web service detection + technology fingerprinting:** ``` …
Read the whole file at its exact version.
How to install
mdr add dreadnode/capabilities/reconnaissance-planning@sha256:ba10c3421543aae4The line at the top of this page pins the label git:20260611.414f191, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_g3ap3tdtuav2koyh)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jun 11, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4195 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
dreadnode/capabilities · 22 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_g3ap3tdtuav2koyh GET https://markdownregistry.com/api/v1/resolve?ref=dreadnode/capabilities/reconnaissance-planning GET https://markdownregistry.com/api/v1/blob/ba10c3421543aae43818cab9fe6ce3cbb95a0f8f4527c12804cc06b230186351
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.