Leaderboard/Security/Claude-OSINT
Last commit on August 24, 2026·Created on April 26, 2026

elementalsouls/Claude-OSINT

A structured framework for automating external reconnaissance and bug bounty engagements
Combined rank
#152
across all skills
In Security
#9
category rank
Stars
2.6k
+1.4% in last 7d
Forks
475
+0.2% in last 7d
Watchers
14
0.0% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

Claude-OSINT provides a set of specialized skills designed for authorized red-team operations and security research. It transforms the LLM into an operator capable of executing multi-stage reconnaissance pipelines, from initial discovery to secret scanning.

The system helps security researchers automate the tedious aspects of external reconnaissance, ensuring that methodology is applied consistently across authorized domains while managing engagement folders and data collection.

WHO IT'S FOR
Bug bounty hunters
automate external reconnaissance for authorized targets
Red team operators
execute end-to-end OSINT engagement pipelines
Security researchers
scan for leaked secrets and credentials
Offensive security engineers
build and validate custom OSINT tradecraft
Repository contents

10 skill files

Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill collection

Follow the documented setup, then try a first task.

I’m using

Claude Code — direct copy of all eight skills

Installs: Complete eight-skill claude-osint bundle. · Claude Code

Before you start
  • Claude Code
  • Git
  1. In a terminal, clone the repository, enter it, populate the full skill content, and copy all eight skill directories into Claude Code's local skills directory.

    # Install all 8 skills (one-time, after clone)
    git clone https://github.com/elementalsouls/Claude-OSINT.git
    cd Claude-OSINT
    chmod +x ./scripts/sync-skill-content.sh
    ./scripts/sync-skill-content.sh
    mkdir -p ~/.claude/skills
    cp -r skills/* ~/.claude/skills/
    ls ~/.claude/skills/
README.md · Checked Sep 18, 2026

Give it something to do.

Suggested first task

Evaluate SPF and DMARC spoofability

Uses email-domain-security

  • An owned or written-authorized domain
  • Raw SPF TXT record
  • Raw DMARC TXT record, or an explicit statement that no record exists
Use the email-domain-security skill to assess the raw SPF and DMARC TXT records below. Give the composite spoofability verdict, severity, attack vector, and confidence, and explain whether the visible header From is protected. Do not send email or perform SMTP checks. Domain: <authorized-domain>. SPF TXT: <raw-SPF-record>. DMARC TXT: <raw-DMARC-record-or-no-record>.
Suggested first task

Decode and screen an AWS account ID offline

Uses cloud-saas-exposure

  • An AKIA, ASIA, or AROA access-key ID already lawfully held
Use the cloud-saas-exposure skill to decode the AWS account ID from this AKIA, ASIA, or AROA access-key ID entirely offline: <access-key-ID-lawfully-held>. Screen the decoded value against the documented AWS example-account IDs and label the result as a lead rather than proof of ownership. Do not make network or AWS API calls.
Suggested first task

Quantify an existing recon finding set

Uses exposure-risk-quantification

  • A completed set of recon findings
  • Associated assets
  • Severity, confidence, ownership, and proof annotations where available
  • Optional breach-record counts separated by source
Use the exposure-risk-quantification skill to compute and explain a defensible 0–100 risk score and A–F grade for the completed finding set below. Apply the ownership and proof demotion cap, show the Exposure, Threat, and Impact inputs, and clearly identify missing evidence. Use only the supplied findings and make no network calls. Findings: <completed-findings-with-severity-confidence-ownership-and-proof>. Assets: <associated-assets>. Optional breach-record counts by source: <counts-or-none>.