mcpField
O
osint

osint

github.com/transilienceaiSecurity600240 installsUpdated 13w ago
Repository

About osint

osint is a security skill for public-source intelligence gathering focused on code repositories, developer footprints, and exposed credentials. It combines repository inventory, code and Git history scanning, and configuration analysis, saving results as structured records and reports.

Key features

  1. 01Enumerate organizations and linked accounts
  2. 02Inventory repository stacks and infrastructure clues
  3. 03Scan current code and Git history for secrets
  4. 04Extract APIs, authentication patterns, and services
  5. 05Check dependencies for CVE candidates

Use cases

  1. 01Investigate an organization's public repositories
  2. 02Find credentials in code or commit history
  3. 03Identify infrastructure and risks from configs and dependencies

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/transilienceai/communitytools --skill osint

After installing, type/osintin Claude Code to confirm it loaded.

Bundled filesreference/repository-recon.md

Details

From the project README

OSINT

Passive and semi-passive intelligence gathering focused on code repositories, developer footprints, and exposed secrets across public platforms.

Phases

1. Organization Discovery
  • Enumerate GitHub/GitLab/Bitbucket orgs for target company name variants
  • Find employee personal accounts linked to the target org
  • Identify archived, forked, and deleted repositories
2. Repository Analysis
  • Map all repos: tech stack, languages, CI/CD, dependencies
  • Identify internal hostnames, IPs, endpoints, environment names
  • Check for .env, config files, secrets in current code
3. Secret & Credential Scanning
  • Scan current code with gitleaks / trufflehog
  • Scan full git history (secrets removed in commits are still accessible)
  • Search with targeted dorks (see reference/repository-recon.md)
4. Code Intelligence
  • Extract API endpoints, auth patterns, internal service names
  • Review Dockerfiles, CI configs, IaC for infra details
  • Check dependency files for version-specific CVE candidates

Output

data/reconnaissance/repositories.json   # Repo inventory + findings
reports/reconnaissance_report.md        # OSINT section appended
raw/osint/                              # Raw tool outputs

Tools

trufflehog, gitleaks, gitrob, GitHub/GitLab search, gh CLI, git log

Rules

  1. Passive discovery first (search APIs, public pages) before any cloning
  2. Scan git history — deleted secrets are still in commit objects
  3. Check employee personal accounts, not just org accounts
  4. Document every discovered credential/secret immediately as a finding
  5. All output saved to {OUTPUT_DIR}/ per CLAUDE.md directory structure

Reference

  • reference/repository-recon.md - Dorks, tool commands, secret patterns, workflow

Comments

Markdown supported