Agent skill

Recon Playbook

A skill your agent uses when starting or restructuring an authorized external web and API assessment.

MITAuto-check passedSecurity

Install Recon Playbook

skills CLI

$ npx skills add uphiago/recon-skills --skill recon-playbook -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install uphiago/recon-skills recon-playbook --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/uphiago/recon-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/meta/recon-playbook .claude/skills/recon-playbook && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "recon-playbook" agent skill from https://github.com/uphiago/recon-skills/tree/main/meta/recon-playbook into .claude/skills/recon-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recon-playbook", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/uphiago/recon-skills/tree/main/meta/recon-playbook

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add uphiago/recon-skills --skill recon-playbook -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install uphiago/recon-skills recon-playbook --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/uphiago/recon-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/meta/recon-playbook .agents/skills/recon-playbook && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "recon-playbook" agent skill from https://github.com/uphiago/recon-skills/tree/main/meta/recon-playbook into .agents/skills/recon-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recon-playbook", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add uphiago/recon-skills --skill recon-playbook -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install uphiago/recon-skills recon-playbook --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/uphiago/recon-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/meta/recon-playbook .cursor/skills/recon-playbook && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "recon-playbook" agent skill from https://github.com/uphiago/recon-skills/tree/main/meta/recon-playbook into .cursor/skills/recon-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recon-playbook", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/uphiago/recon-skills.git --path meta/recon-playbook

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add uphiago/recon-skills --skill recon-playbook -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install uphiago/recon-skills recon-playbook --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/uphiago/recon-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/meta/recon-playbook .gemini/skills/recon-playbook && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "recon-playbook" agent skill from https://github.com/uphiago/recon-skills/tree/main/meta/recon-playbook into .gemini/skills/recon-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recon-playbook", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install uphiago/recon-skills recon-playbook

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add uphiago/recon-skills --skill recon-playbook -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/uphiago/recon-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/meta/recon-playbook .github/skills/recon-playbook && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "recon-playbook" agent skill from https://github.com/uphiago/recon-skills/tree/main/meta/recon-playbook into .github/skills/recon-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recon-playbook", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add uphiago/recon-skills --skill recon-playbook -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install uphiago/recon-skills recon-playbook --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/uphiago/recon-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/meta/recon-playbook .opencode/skills/recon-playbook && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "recon-playbook" agent skill from https://github.com/uphiago/recon-skills/tree/main/meta/recon-playbook into .opencode/skills/recon-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recon-playbook", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: recon-playbook
GitHub stars: 1.3k
Token cost: ~1.9k tokens
SKILL.md length: 600 words
Files: 1
Skills in repo: 23
Repo updated: Sep 1, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when starting or restructuring an authorized external web and API assessment.

Works in 8 steps: Record Scope → Discover and Normalize Assets → Resolve and Identify HTTP Services → …
Restructuring an authorized external web and API assessment
SKILL.md covers When to Use, Prerequisites, How to Run and Procedure, plus 2 more sections
Calls jq and curl; reaches crt.sh

What it does

Recon Playbook is an agent skill from uphiago/recon-skills. Use when starting or restructuring an authorized external web and API assessment.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires curl, jq, subfinder, dnsx, httpx, katana, and optional nmap

It sits in Security, covering Bug bounty. The repository describes itself as: Recon & pentest skill pack. CORS, XSS, SQLi, SSRF, RCE, WordPress, MCP, cloud, subdomain takeover, and more. Field-tested. MIT. Full write-up at hiago.sh. The licence is MIT.

When your agent uses it

Restructuring an authorized external web and API assessment
Tasks that involve Bug bounty

Example prompts

“/recon-playbook”

Requirements

Compatibility (from SKILL.md): Requires curl, jq, subfinder, dnsx, httpx, katana, and optional nmap

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Record Scope
Discover and Normalize Assets
Resolve and Identify HTTP Services
Map Routes, Parameters, and Client Code
Map APIs and Identity Boundaries
Select Focused Skills
Validate One Hypothesis at a Time
Preserve Evidence

What it can do on your machine

Read from SKILL.md and the folder at commit 1260244. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- jq
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- crt.sh
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires curl, jq, subfinder, dnsx, httpx, katana, and optional nmap
From compatibility in the SKILL.md frontmatter.

Context cost

Recon Playbook loads about 1.9k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 600 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~24
When it runs · the whole SKILL.md, loaded when a task matches: ~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from uphiago/recon-skills at commit 1260244, republished under its MIT licence (© uphiago). 600 words, ~1,876 tokens.

Download SKILL.mdSave it as .claude/skills/recon-playbook/SKILL.md (or your agent's skills folder).

name: recon-playbook
description: Use when starting or restructuring an authorized external web and API assessment.
compatibility: Requires curl, jq, subfinder, dnsx, httpx, katana, and optional nmap
version: 2.0.0
license: MIT
platforms: linux, macos
tags: meta, recon, web, api, workflow
category: meta
related_skills: attack-patterns-reference, evidence-hygiene, offensive-osint, port-service-discovery, report-writing, subdomain-enumeration, triage-validation…

External Web Recon Playbook

Use this playbook to turn an authorized root domain or asset list into a prioritized map of web applications, APIs, authentication boundaries, and testable security hypotheses.

text

scope
  -> assets
  -> DNS and services
  -> routes and client code
  -> APIs and identities
  -> hypotheses
  -> focused validation
  -> evidence and reporting

When to Use

Beginning an external web, API, or bug bounty assessment.
Recon output exists but lacks normalization, provenance, or prioritization.
The target spans multiple applications, subdomains, or identity boundaries.
A broad scan needs to be converted into focused manual validation.

Do not use this playbook to justify activity outside the agreed scope or to run every available tool against every asset.

Prerequisites

Explicit authorization, target boundaries, exclusions, rate limits, and stop conditions.
curl, jq, subfinder, dnsx, httpx, and katana.
nmap only when IP or port discovery is in scope.
Approved test identities for authorization and session testing.
A writable evidence directory.

How to Run

bash

export TARGET="example.test"
export OUTPUT_DIR="${OUTPUT_DIR:-./output/$TARGET}"

mkdir -p \
  "$OUTPUT_DIR/assets" \
  "$OUTPUT_DIR/http" \
  "$OUTPUT_DIR/urls" \
  "$OUTPUT_DIR/evidence"

Run each phase only after reviewing the preceding output. Keep raw source files so every hostname, URL, and hypothesis has provenance.

Procedure

1. Record Scope

Keep a short operator-readable scope record beside the output:

text

allowed: *.example.test
excluded: status.example.test
identities: anonymous, test-user-a, test-user-b
request rate: 2 requests/second/host
state changes: synthetic records only

The scope must answer what may be tested, which identities may be used, how much traffic is acceptable, and whether a state-changing test is allowed.

2. Discover and Normalize Assets

bash

subfinder -d "$TARGET" -silent \
  > "$OUTPUT_DIR/assets/subfinder.txt"

curl -sS --max-time 30 \
  "https://crt.sh/?q=%25.${TARGET}&output=json" \
  | jq -r '.[].name_value' \
  | sed 's/^\*\.//' \
  > "$OUTPUT_DIR/assets/crtsh.txt"

cat "$OUTPUT_DIR/assets/subfinder.txt" \
    "$OUTPUT_DIR/assets/crtsh.txt" \
  | tr '[:upper:]' '[:lower:]' \
  | grep -E '^[a-z0-9.-]+\.[a-z]{2,}$' \
  | sort -u \
  > "$OUTPUT_DIR/assets/hostnames.txt"

Review wildcard results, certificate SANs, third-party CNAMEs, and excluded assets before active probing.

3. Resolve and Identify HTTP Services

bash

dnsx \
  -l "$OUTPUT_DIR/assets/hostnames.txt" \
  -silent -a -aaaa -cname -json \
  -o "$OUTPUT_DIR/assets/dns.jsonl"

httpx \
  -l "$OUTPUT_DIR/assets/hostnames.txt" \
  -threads 10 \
  -rate-limit 2 \
  -status-code -title -tech-detect -server -ip -cname \
  -json \
  -o "$OUTPUT_DIR/http/services.jsonl"

jq -r '.url // empty' "$OUTPUT_DIR/http/services.jsonl" \
  | sort -u \
  > "$OUTPUT_DIR/http/live-urls.txt"

Treat technology labels and banners as routing signals. Confirm important components from more than one source before associating a vulnerability.

4. Map Routes, Parameters, and Client Code

bash

katana \
  -list "$OUTPUT_DIR/http/live-urls.txt" \
  -silent -jc -kf all \
  -c 2 -p 2 -rl 2 \
  -o "$OUTPUT_DIR/urls/katana.txt"

grep -Ei '/api/|/graphql|swagger|openapi|/rest/' \
  "$OUTPUT_DIR/urls/katana.txt" \
  > "$OUTPUT_DIR/urls/api-candidates.txt"

grep -Ei 'login|logout|register|reset|oauth|saml|callback|session|token' \
  "$OUTPUT_DIR/urls/katana.txt" \
  > "$OUTPUT_DIR/urls/auth-candidates.txt"

grep -Ei '\.js([?#].*)?$' "$OUTPUT_DIR/urls/katana.txt" \
  > "$OUTPUT_DIR/urls/javascript.txt"

Map current routes before adding archive sources. Historical URLs are useful for discovery, but they do not prove that an endpoint remains reachable.

5. Map APIs and Identity Boundaries

For each application, record:

API base URLs, descriptions, versions, operations, and object identifiers;
anonymous, user, tenant, manager, and administrator boundaries;
login, logout, refresh, password reset, MFA, OAuth, and SAML flows;
cookie, token, CORS, CSRF, and WebSocket behavior;
state-changing methods and the synthetic objects approved for testing.

Authorization testing needs at least two approved identities when the claim depends on cross-user or cross-tenant access.

Show full SKILL.md (263 more words)Show less

6. Select Focused Skills

Use attack-patterns-reference to classify observations, then open only the skills supported by current evidence. Common routes include:

Observation	Follow-up skill
JavaScript bundles or source maps	`js-secrets-extraction`, `source-leak-hunt`
REST objects and identifiers	`hunt-api-misconfig`, `hunt-idor`
GraphQL endpoint	`hunt-graphql`
OAuth or SAML flow	`hunt-oauth`, `hunt-saml`
WordPress surface	`hunt-wordpress`, `wordpress-plugin-hunt`
Public service port	`port-service-discovery`
Candidate multi-step path	`cross-attack-chains`

7. Validate One Hypothesis at a Time

Write the hypothesis before the probe:

text

Expected: user A cannot read user B's synthetic object.
Test: repeat the same object request with both approved sessions.
Positive evidence: user A receives user B's object and its non-public fields.
Negative control: an unknown object returns the documented not-found response.
Stop condition: any access to non-synthetic or out-of-scope data.

Use triage-validation before reporting. A status code, scanner label, version string, or permissive-looking header is not sufficient by itself.

8. Preserve Evidence

For every material result, retain:

target, identity, UTC timestamp, and scope context;
sanitized request and response;
expected and observed behavior;
negative control;
side effects, cleanup, and testing limits;
tool and relevant version.

Use evidence-hygiene while testing and report-writing after validation.

Pitfalls

Catch-all applications return 200 for nonexistent sensitive paths.
CDN IPs and headers do not identify an origin or application version alone.
Archived endpoints may be dead, redirected, or reassigned.
Public client identifiers are not automatically secrets.
Broad crawling can cross into third-party or excluded domains.
Pagination can turn a bounded proof into unnecessary data collection.
State-changing validation requires explicit authorization immediately before the command and must use synthetic records.

Verification

Every active asset traces back to an allowed scope entry and discovery source.
Live services have normalized URLs and DNS context.
Application maps include routes, APIs, authentication, and identity roles.
Every promoted finding includes semantic evidence and a negative control.
Candidate attack paths label unverified steps as inferred or not tested.
Evidence is sanitized, reproducible, and stored beneath OUTPUT_DIR.

Files

Just SKILL.md in meta/recon-playbook of uphiago/recon-skills.

Open the folder on GitHubat commit 1260244

Compare with similar skills

Recon Playbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Recon Playbook compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Recon Playbook this skilluphiago/recon-skills	1.3k	—	~1.9k	Automated safety check: Pass	MIT	1 mo ago
Web3 Smart Contract Auditawarexone/Agentic-Bug-Hunter	5.3k	3 repos	~4.5k	Automated safety check: Pass	MIT	today
Bug Bounty Hunting Methodologyawarexone/Agentic-Bug-Hunter	5.3k	2 repos	~4.7k	Automated safety check: Pass	MIT	today
Metabigor OSINT Reconj3ssie/metabigor	1.9k	—	~2.4k	Automated safety check: Pass	MIT	2 mo ago
Wooyun Legacytanweai/wooyun-legacy	1.8k	—	~1.9k	Automated safety check: Pass	Custom licence	2 mo ago
Client Request Signature Reversalawarexone/Agentic-Bug-Hunter	5.3k	—	~4.7k	Automated safety check: Pass	MIT	today

Similar skills

Web3 Smart Contract Audit
awarexone/Agentic-Bug-Hunter
Guides smart contract audits and bounty target selection with ten DeFi bug classes, kill signals, a Foundry PoC template and grep patterns.
5.3k GitHub starsUsed in 3 repos~4.5k tokens
SecurityAuto-check passed
Bug Bounty Hunting Methodology
awarexone/Agentic-Bug-Hunter
Orchestrates a bug bounty session with a 5-phase workflow and a critical-thinking framework covering developer psychology, anomaly detection and What-If experiments.
5.3k GitHub starsUsed in 2 repos~4.7k tokens
SecurityAuto-check passed
Metabigor OSINT Recon
j3ssie/metabigor
Operates the metabigor CLI to map a target's network ranges, subdomains, ports, related domains, CDNs and archived URLs from free sources without API keys.
1.9k GitHub stars~2.4k tokensUpdated 2 mo ago
SecurityAuto-check passed
Wooyun Legacy
tanweai/wooyun-legacy
WooYun business logic vulnerability methodology — 22,132 real cases across 6 domains (authentication bypass, authorization bypass, payment tampering, information disclosure, logic flaws…
1.8k GitHub stars~1.9k tokensUpdated 2 mo ago
SecurityAuto-check passed
Client Request Signature Reversal
awarexone/Agentic-Bug-Hunter
Recovers a client-side request signature or anti-bot token just far enough to replay blocked requests in bug bounty testing, starting from a captured packet.
5.3k GitHub stars~4.7k tokensUpdated today
SecurityAuto-check passed
Web3 Bug Bounty AI Tools
tradecatlabs/vibe-coding-cn
A selection guide to AI-driven tools for Web3 bug bounty work, from autonomous web pentesters to smart contract bug finders, with notes on authorization.
17k GitHub starsUsed in 2 repos~3.9k tokens
SecurityAuto-check: warnings

Questions about Recon Playbook

What does Recon Playbook do?

A skill your agent uses when starting or restructuring an authorized external web and API assessment. Recon Playbook is an agent skill from uphiago/recon-skills. Use when starting or restructuring an authorized external web and API assessment.

When should I use Recon Playbook?

Recon Playbook fits situations like: restructuring an authorized external web and API assessment; tasks that involve Bug bounty.

How do I install Recon Playbook in Claude Code?

Run `npx skills add uphiago/recon-skills --skill recon-playbook -a claude-code`. Or copy the skill folder (meta/recon-playbook in uphiago/recon-skills) into .claude/skills/recon-playbook in your project. Claude Code loads it when a task matches its description.

How do I install Recon Playbook in Codex?

Run `npx skills add uphiago/recon-skills --skill recon-playbook -a codex`. Or copy the skill folder (meta/recon-playbook in uphiago/recon-skills) into .agents/skills/recon-playbook in your project. Codex loads it when a task matches its description.

Can I use Recon Playbook in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add uphiago/recon-skills --skill recon-playbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/recon-playbook, .gemini/skills/recon-playbook, .github/skills/recon-playbook and .opencode/skills/recon-playbook in your project.

What does Recon Playbook need to run?

Going by SKILL.md and its folder, Recon Playbook needs the command-line tools its instructions call (jq and curl). Compatibility (from SKILL.md): Requires curl, jq, subfinder, dnsx, httpx, katana, and optional nmap.

Does Recon Playbook access the network?

SKILL.md names 1 domain. In commands or code: crt.sh; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Recon Playbook safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Recon Playbook use?

Recon Playbook is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Recon Playbook use?

About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Recon Playbook?

Skills that share tags, products or a category with Recon Playbook: Web3 Smart Contract Audit (awarexone/Agentic-Bug-Hunter, 5.3k stars), Bug Bounty Hunting Methodology (awarexone/Agentic-Bug-Hunter, 5.3k stars), Metabigor OSINT Recon (j3ssie/metabigor, 1.9k stars) and Wooyun Legacy (tanweai/wooyun-legacy, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Recon Playbook?

uphiago (a GitHub user) maintains it in uphiago/recon-skills, which has 1,293 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on September 1, 2026.

Source: uphiago/recon-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Recon Playbook

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

External Web Recon Playbook

When to Use

Prerequisites

How to Run

Procedure

1. Record Scope

2. Discover and Normalize Assets

3. Resolve and Identify HTTP Services

4. Map Routes, Parameters, and Client Code

5. Map APIs and Identity Boundaries

6. Select Focused Skills

7. Validate One Hypothesis at a Time

8. Preserve Evidence

Pitfalls

Verification

Files

Compare with similar skills

Similar skills

More from uphiago/recon-skills

Related

Questions about Recon Playbook