Individual skill
what-leaked-about-you
Check and interpret data-breach exposure for an email, username, phone or name using Have I Been Pwned, the Pwned Passwords k-anonymity range API, DeHashed, IntelX and Snusbase. Use when checking breach or leak exposure, finding which services an account was registered with, interpreting a combolist or credential dump, assessing credential compromise, or auditing your own leaked personal data. Applies to incident response and account-takeover triage, executive and VIP protection, pre-employment and vendor risk screening, and personal privacy audits. Reference at useosint.com/skills/what-leaked-about-you.
skills/what-leaked-about-you/SKILL.md
Source commit 06243a5620b0c9c97502edd4ee9e31995a3bdccd
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 61
- Repository last updated
- Aug 3, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- claude Repository topic
- claude-skills Repository topic
- cursor Repository topic
- cursor-skills Repository topic
- cybersecurity Repository topic
- digital-forensics Repository topic
- due-diligence Repository topic
- geoint Repository topic
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 11,914 bytesSKILL.mdcore · 11,914 bytesSKILL.mdcore · 11,914 bytesSKILL.mdcore · 11,914 bytesSKILL.mdcore · 11,914 bytesSKILL.mdcore · 11,914 bytesSKILL.mdcore · 11,914 bytesSKILL.mdcore · 11,914 bytesSKILL.mdcore · 11,914 bytesreference/record-fields.mddoc · 6,182 bytesreference/source-catalogue.mddoc · 6,233 bytes
Read excerpt
# What leaked about you
Breach data answers a question nothing else answers cheaply: which services did
this identity actually use. That service list is almost always worth more to an
investigator than the credentials in the record — and the credentials are the
part you must never touch. Using a leaked password is unauthorized access, no
matter how public the dump was.
## What a record actually contains, and what matters
A breach record is a row from a service's user table. Typical fields: email,
username, a password hash (or plaintext, in bad cases), registration date, last
login, IP address at signup, display name, date of birth, physical address,
security questions, and whatever the service happened to collect.