offensive-osint

Provides probes, wordlists, regexes, and dorks for authorized external reconnaissance and bug-bounty asset discovery.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/inventashif/helpful-code-sidekick --skill offensive-osint-inventashif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: offensive-osint
Source: https://github.com/inventashif/helpful-code-sidekick/tree/main/scripts/hackerai/skills/bughunter/offensive-osint
Command: npx skills add https://github.com/inventashif/helpful-code-sidekick --skill offensive-osint-inventashif

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Security researchers and bug-bounty hunters need concrete, ready-to-use reconnaissance material — probe paths, secret regexes, dork templates, and severity rubrics — instead of assembling this operational knowledge from scratch for every engagement. ## Core Features & Use Cases - Recon Arsenal: 15 modular reference files covering subdomain enumeration, Swagger/GraphQL discovery, cloud bucket enumeration (S3/GCS/Azure), identity-fabric fingerprinting (Entra/Okta/ADFS/M365), CDN/WAF bypass, and vendor product fingerprinting. - Secret Detection & Triage: A 48-pattern secret-regex catalog (AWS, GitHub, Stripe, Anthropic, OpenAI, npm, PyPI, and more) plus read-only validators and a runnable stdlib-only Python scanner (scripts/secret_scan.py). - Scoring & Reporting: A 0–100 endpoint interest rubric, mobile app ownership confidence scoring, 27 attack-path hint templates, and an 80+ example severity decision matrix. - Use Case: During an authorized bug-bounty engagement against target.com, load the skill to enumerate subdomains, probe for exposed Swagger and GraphQL endpoints, scan JavaScript for leaked secrets, and score each finding's severity with consistent evidence formatting. ## Quick Start Ask the assistant to perform an external reconnaissance pass on an authorized target domain, for example: run external recon on target.com including subdomain enumeration, exposed API discovery, and secret scanning.

Frequently Asked Questions about offensive-osint

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

FAQPage Schema
How do I enumerate subdomains for a bug bounty target?

Subdomain enumeration combines passive sources (crt.sh, Censys, Subfinder, OTX) with active prefix probing using wordlists like Assetnote or SecLists. Passive enumeration alone misses 20-40% of high-value subdomains, so always pair it with an active prefix sweep.

How do I find leaked API keys and secrets in a target's code?

Use the 48-pattern secret regex catalog covering AWS, GitHub, Stripe, Slack, Anthropic, OpenAI, npm, PyPI, and others, or run the bundled stdlib-only Python scanner against a directory, file list, or piped input. Validate any hits with read-only liveness checks only.

What paths should I probe to find Swagger or GraphQL endpoints?

Probe 28 common Swagger/OpenAPI paths and 13 GraphQL paths, then POST a standard introspection query to discovered GraphQL endpoints. If introspection is disabled, use field-suggestion enumeration with alias batching to map the schema.

Does this skill work for targets without authorization?

No. The skill explicitly requires that assets are owned by the operator or covered by written authorization, and it excludes active exploitation, post-exploitation, and destructive probes. It is scoped to reconnaissance only.

How do I score the severity of a discovered API endpoint?

Apply the 0-100 endpoint interest rubric: unauthenticated write access adds 40 points, open GraphQL introspection 35, reflected CORS with credentials 25, and so on. Scores of 90 or above map to CRITICAL, 70-89 to HIGH, with an attack-path hint attached for scores of 70 or more.

What are the limitations of the HudsonRock breach data lookups?

The free HudsonRock Cavalier API returns counts and sample URLs only, redacts subdomain hostnames past the first few entries, and never exposes cleartext credentials. It rate-limits to roughly one request per second per IP, and unredacted data requires the paid tier.