recon-for-sec

Plan reconnaissance workflows for new security testing targets.

11|4|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/sayseven7/frameseven --skill recon-for-sec-sayseven7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recon-for-sec
Source: https://github.com/sayseven7/frameseven/tree/main/internal/mcp/skills/recon-for-sec
Command: npx skills add https://github.com/sayseven7/frameseven --skill recon-for-sec-sayseven7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps security testers begin with a structured reconnaissance path instead of guessing where to probe first. It turns an unfamiliar target into a prioritized map of assets, technologies, endpoints, and next-step testing routes.

Core Features & Use Cases

  • Scope and target-type confirmation: Establishes what is in bounds before active testing begins.
  • Reconnaissance planning: Guides asset discovery, port and service identification, technology fingerprinting, and endpoint inventory.
  • Follow-up routing: Helps decide whether the next best step is API security, authentication testing, injection checking, or business-logic review.
  • Use case: Use this when a new target arrives and you need a disciplined methodology for choosing high-value tests without random payload enumeration.

Quick Start

Ask the Skill to map a new target’s attack surface, confirm scope, and recommend the first security testing path.

Frequently Asked Questions about recon-for-sec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan reconnaissance for an unknown attack surface?

Reconnaissance planning maps new targets by confirming scope, discovering assets, identifying services, and fingerprinting technologies. It provides a prioritized test-path routing instead of relying on random payload enumeration across unfamiliar endpoints.

What is the best way to confirm scope before starting security testing?

Scope confirmation establishes exactly what assets are in bounds before any active testing begins. This ensures your reconnaissance workflow only maps authorized targets, preventing accidental probing of out-of-bounds infrastructure during asset discovery.

How do I prioritize which security test to run after endpoint discovery?

After endpoint discovery, you prioritize tests using follow-up routing to decide whether to target API security, authentication, injection, or business-logic assessments. This routes your testing efforts toward the highest-value attack surface areas first.

Can I use this for technology fingerprinting and service identification?

Yes, you can use this for technology fingerprinting and service identification. The reconnaissance workflow includes port and service identification alongside technology fingerprinting to build a complete inventory of the target's exposed attack surface.

Does this reconnaissance method support routing into API security testing?

Yes, this reconnaissance method supports structured follow-up routing directly into API security testing. After mapping the attack surface and inventorying endpoints, it recommends whether API, authentication, injection, or business-logic assessments are the best next step.

When should I not use automated attack surface mapping?

You should not use automated attack surface mapping when you lack authorized permission for the target scope. The methodology relies on authorized reconnaissance methods, meaning you must complete scope confirmation to ensure all asset discovery stays within approved testing boundaries.