cybersecurity-bodyguardlisted

# Cybersecurity Bodyguard Active **defense** against doxxing, stalking, and targeted harassment. This skill does three things: 1. **Passive OSINT self-scan** -- what the internet knows about Alex right now 2. **Outbound exposure audit** -- catch PII leaks before they ship 3. **Incident response** -- playbooks for when something is actively going wrong ## Config: what to monitor PII to monitor lives in a gitignored config at `.claude/skills/cybersecurity-bodyguard/targets.json`. If that file is missing, read `targets.example.json` and prompt Alex to fill it in. The config lists: - Legal name + common variants - Email addresses (personal, work, throwaway) - Phone numbers (current + prior) - Physical addresses (current + prior 5 years -- stalkers use old addresses) - Usernames/handles across platforms - Date of birth - Partner's name + identifiers (optional -- stalkers pivot through family) - Employer name - Known aliases and pen names Never commit this file. Never read it into a response to the user verbatim -- refer to entries by key (e.g., "email[0]") when showing scan results. ## Mode 1: Passive OSINT self-scan Triggered by: "bodyguard scan", "what's public about me", "doxx scan", weekly schedule, or incident response. ### Scan steps Run in parallel where possible: 1. **Credential breaches** -- query Have I Been Pwned for each email in targets.json. Report new breaches since the last scan (compare against `Security Log.md`). 2. **Google dorking** -- run these sear