OSINT

SkillDev tools

Lets your agent gather public intelligence on a company's code repos, exposed secrets, and developer footprint.

Then ask your AI: use the OSINT skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.

About this skill

Open-source intelligence gathering - company repository enumeration, secret scanning, git history analysis, employee footprint, and code exposure discovery.

What this skill tells your AI

The instructions your AI receives, as published by transilienceai/communitytools in skills/osint/SKILL.md and read by Ahel’s review.

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

Signals

GitHub stars
562
Forks
80
Last commit
Jul 2026
Advanced
Item type
skill
Key
osint-transilienceai
Source
github.com/transilienceai/communitytools