offensive-osint

Provides probe paths, regexes, dorks, and scoring rubrics for authorized external reconnaissance.

Updated May 29, 2026
One-click install
npx skills add https://github.com/hhjkjkjk/Claude-skills --skill offensive-osint-hhjkjkjk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: offensive-osint
Source: https://github.com/hhjkjkjk/Claude-skills/tree/main/skills/offensive-osint
Command: npx skills add https://github.com/hhjkjkjk/Claude-skills --skill offensive-osint-hhjkjkjk

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Red-team operators and bug-bounty hunters waste time reconstructing probe wordlists, secret regexes, and enumeration endpoints from scratch for every engagement. This Skill centralizes the concrete operational data needed for authorized external reconnaissance into one indexed arsenal. ## Core Features & Use Cases - Probe & Wordlist Arsenal: 28 Swagger/OpenAPI paths, 13 GraphQL paths with introspection body, 35 high-risk ports, cloud-bucket permutation generator (S3/GCS/Azure), and copy-paste curl one-liners for 15 always-on HTTP checks. - Secret & Identity Intelligence: 48-pattern secret regex catalog (AWS, GitHub, Stripe, Anthropic, OpenAI, npm, PyPI), 9 read-only secret validators, and concrete identity-fabric endpoints for Entra, Okta, ADFS, Google Workspace, and M365 deep enumeration. - Scoring & Triage Rubrics: 0-100 endpoint interest score, mobile app ownership confidence rubric, 27 attack-path hint templates, and an 80+ example severity decision matrix. - Use Case: During an authorized bug-bounty engagement against example.com, load the probes reference to enumerate subdomains and exposed .git/.env files, validate a leaked GitHub PAT read-only, then score each discovered endpoint and emit severity-tagged findings with evidence hashes. ## Quick Start Ask the AI to run an external recon pass on an authorized target domain using the offensive-osint probes, wordlists, and severity rubric.

Frequently Asked Questions about offensive-osint

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

FAQPage Schema
How do I find exposed Swagger or GraphQL endpoints on a target?▼

Probe the 28 Swagger/OpenAPI paths and 13 GraphQL paths in the probes-and-wordlists reference against every alive webapp. For GraphQL, POST the standard introspection query; if introspection is disabled, fall back to field-suggestion enumeration with tools like Clairvoyance.

How do I validate a leaked API key without causing damage?▼

Use the 9 read-only validators in the secret-validators reference, covering AWS STS GetCallerIdentity, GitHub PAT scope headers, Slack auth.test, Postman, Anthropic, OpenAI, npm, Atlassian, and DataDog. Each call only reads account metadata and never modifies state.

What regex patterns detect leaked AWS or GitHub credentials?▼

The secret-patterns reference contains 48 regexes with severity and false-positive notes, including AKIA/ASIA prefixes for AWS keys and ghp_/github_pat_ prefixes for GitHub tokens. A stdlib-only Python scanner, secret_scan.py, mirrors the catalog and outputs JSONL findings.

Does this skill work for targets without written authorization?▼

No. The skill explicitly requires operator ownership or written authorization before use, and excludes active exploitation, post-exploitation, and defensive detection content. It is scoped strictly to reconnaissance on authorized assets.

How is the severity of a discovered endpoint determined?▼

Apply the 0-100 endpoint interest rubric: unauthenticated write methods add 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 high scores.

What are the limitations of the free HudsonRock breach API?▼

The free Cavalier API returns counts and sample URLs only, redacts subdomain hostnames with asterisks, never exposes cleartext passwords, and rate-limits to roughly one request per second per IP. Unredacted credentials and bulk enumeration require the paid tier.