osint

Enumerate repositories, scan for secrets, and map employee footprints across public sources.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/YukiIto1999/ctf-sleuth --skill osint-yukiito1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: osint
Source: https://github.com/YukiIto1999/ctf-sleuth/tree/main/.claude/skills/osint
Command: npx skills add https://github.com/YukiIto1999/ctf-sleuth --skill osint-yukiito1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps security analysts automatically discover and map open-source information about a target by enumerating repositories, scanning for secrets, and revealing employee footprints across public platforms to support risk assessments and incident response.

Core Features & Use Cases

  • Organization and repository discovery across GitHub, GitLab, and Bitbucket to identify variants and exposed assets.
  • Secret & credential scanning across current code and historical commits to surface hidden data.
  • Code intelligence to extract endpoints, internal service names, and infrastructure clues from repositories.
  • Output delivery as structured data suitable for automation and human-readable reports to support audits and security reviews.
  • Use Case: conducting an external security review of a company’s code exposure and governance posture.

Quick Start

Run the osint skill to enumerate repositories, scan for secrets, and generate an OSINT report.

Frequently Asked Questions about osint

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

FAQPage Schema
How do I enumerate repositories and scan for secrets across GitHub, GitLab, and Bitbucket?

To enumerate repositories and scan for secrets, you map public repositories across GitHub, GitLab, and Bitbucket, then scan current code and historical commits to surface exposed credentials and infrastructure clues.

What is the best way to map employee footprints and code exposure for a company OSINT assessment?

Mapping employee footprints and code exposure involves identifying organization assets and employee activities across public repositories to support external security reviews and incident response with structured findings.

Can I extract internal service names and endpoints from historical git history during reconnaissance?

Yes, repository reconnaissance can extract internal service names, endpoints, and infrastructure clues by analyzing historical git history and current code to deliver code intelligence for security audits.

Does secret scanning cover historical commits or just current code in repository reconnaissance?

Secret scanning covers both current code and historical git history commits, ensuring comprehensive code exposure discovery and hidden data surfacing during organization-level reconnaissance.

What format are the OSINT findings delivered in for automation and security audits?

OSINT findings are delivered as structured data suitable for automation and human-readable reports, providing structured outputs that directly support governance posture reviews and risk assessments.