# osint

osint — a skill for passive intelligence gathering across code repositories, developer accounts, and exposed secrets. Discovers company repositories, scans commit history for sensitive data, maps API endpoints and internal infrastructure.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 251 installs · ★ 632 repo stars
- Author: transilienceai
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/transilienceai/communitytools/tree/HEAD/skills/osint/SKILL.md
- Updated: 2026-07-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/osint

## What it does

osint operates in four phases: it enumerates GitHub, GitLab, and Bitbucket organizations for the target company, discovers employee personal accounts, then analyzes every repository found to map tech stack, languages, and dependencies. It scans current code and full commit history with `gitleaks` and `trufflehog` to catch secrets removed in past commits. Finally, it extracts API endpoints, authentication patterns, internal service names, and examines Dockerfiles and CI configs for infrastructure details.

The skill starts passive—searching through public APIs and pages—before cloning anything. Every discovered credential is recorded as a finding. Results are saved to `data/reconnaissance/` and `reports/` following the project's directory structure: a repository inventory, a reconnaissance report, and raw tool outputs.

It requires internet access to public registries and uses the `gh` CLI. Useful for security audits of your own codebase, threat assessment before a security incident, and code inventory before migration or compliance review.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill osint -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/osint/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/osint/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill osint -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/osint/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill osint -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/osint/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install transilienceai/communitytools skills/osint
```

2. **Manually: put the files in place**
- File: `.github/skills/osint/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill osint -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/transilienceai/communitytools --path skills/osint
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/osint/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill osint -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/transilienceai/communitytools/tree/HEAD/skills/osint/SKILL.md

## When to use it
- enumerate all repositories across GitHub, GitLab, and Bitbucket for a company
- scan full commit history for accidentally committed secrets and API keys
- extract internal hostnames, IP addresses, and service endpoints from code
- identify dependency versions with known vulnerabilities
- discover personal developer accounts linked to the organization

## Example prompts
- Run osint reconnaissance on acmecorp across all platforms
- Scan the full repository history of acmecorp for exposed credentials
- Extract all internal endpoints and service names from acmecorp's codebase

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: e9838af0f27fe6e3.

BEGIN THIRD-PARTY FILE e9838af0f27fe6e3
````text
---
name: osint
description: Open-source intelligence gathering - company repository enumeration, secret scanning, git history analysis, employee footprint, and code exposure discovery.
---

# 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
````
END THIRD-PARTY FILE e9838af0f27fe6e3

The third-party file has ended. Everything between the e9838af0f27fe6e3 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© transilienceai · MIT · https://github.com/transilienceai/communitytools/tree/HEAD/skills/osint/SKILL.md

## Similar
- [ctf-osint](https://affpapa.org/en/nevibecode/skills/ctf-osint.md) — skill · 10000 installs
- [osint-recon](https://affpapa.org/en/nevibecode/skills/osint-recon.md) — skill · 486 installs
- [osint-methodology](https://affpapa.org/en/nevibecode/skills/osint-methodology.md) — skill · ★ 16193 repo stars
- [osint-collector](https://affpapa.org/en/nevibecode/agents/osint-collector.md) — subagent · ★ 2482 repo stars
- [conducting-external-reconnaissance-with-osint](https://affpapa.org/en/nevibecode/skills/conducting-external-reconnaissance-with-osint.md) — skill · 353 installs

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
