yaklang/hack-skills

recon-for-sec

>- Entry P1 category router for reconnaissance and methodology. Use when mapping scope, discovering assets, fingerprinting technology, building endpoint inventory, and choosing the first high-value security testing path.

All-time #4312 Trending #7621 First seen Apr 8, 2026
8-week activity · all time api

Installation

$ npx skills add yaklang/hack-skills --skill recon-for-sec

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from yaklang/hack-skills · top by installs.

npx skills add yaklang/hack-skills

Browse all from yaklang/hack-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2.1K
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,385 B
  • docs SUMMARY.md 238 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3,019 installs

SKILL.md

Recon and Methodology Router

This is the starting router for new targets and unknown attack surfaces.

When to Use

  • You just received a new target and do not yet know what to test first
  • You need to begin with asset discovery, tech fingerprinting, endpoint inventory, and test-route planning
  • You want to build follow-up testing on structured methodology instead of random payload enumeration

Skill Map

  • [Recon and Methodology](../recon-and-methodology/SKILL.md)
  • [Insecure Source Code Management](../insecure-source-code-management/SKILL.md) — .git/.svn/.hg exposure detection
  • [Dependency Confusion](../dependency-confusion/SKILL.md) — Supply chain reconnaissance for internal package names

Recommended Flow

  1. First confirm in-scope assets and target type
  2. Then perform asset discovery, port/service identification, technology fingerprinting, and endpoint collection
  3. Route based on collected findings to [api-sec](../api-sec/SKILL.md), [auth-sec](../auth-sec/SKILL.md), [injection-checking](../injection-checking/SKILL.md), or [business-logic-vuln](../business-logic-vuln/SKILL.md)