Agent skill · security · nousresearch
unbroker
Remove your info from data-broker sites, by name or phone.
Why this skill is useful
Adds executable scripts for autonomous data removal from data broker sites, including handling of consent and verification processes.
What it needs
Requires python3 installed locally. Requires browserbase account access. About 11k tokens when loaded. Last updated 2026-08-07. 226,679 stars on the source repository.
What this skill does
unbroker Find where a person's personal information (name, addresses, phone, email, relatives) is exposed on data brokers and people-search sites, then remove it - automatically where possible, with guided human steps only where a site demands a CAPTCHA, government ID, phone call, or fax. Manages multiple people independently. It does not defeat anti-bot systems, does not act on anyone without recorded consent, and does not remove public records (voter/property/court) or accounts the person controls. The Python CLI (scripts/pdd.py) owns the deterministic state - config, dossiers + consent, the broker database, tier planning, the ledger, drafts, reports, email sending (SMTP), verification-link polling (IMAP), and the autonomous action queue (next). You (the agent) do the scanning and form-driving with native tools: webextract and browserexec for searching and web forms, and cronjob for recurring re-scans. Runs can be entered from a phone number alone (spam-call scrubbing), with the FTC Do Not Call registry one-shot (dnc) alongside the opt-outs. Autonomy contract This skill is designed to run hands-off. After intake (+ recorded consent) there are exactly TWO legitimate human touchpoints: (1) the intake conversation itself, and (2) ONE consolidated human-task digest at the end of the run ($PDD tasks). Between those: Never ask the operator to choose configuration. $PDD setup --auto detects capabilities and picks the most autonomous valid config itself. Never pause before individual submissions when autonomy=full (the default): the consent recorded at intake is standing authorization for T0-T2 opt-outs. The one exception: an action carrying confirmfirst: true (always set on dncregister, a registry signup the intake consent does not cover) waits for the operator's yes in every mode. (autonomy=assisted sets confirmfirst on every submission for cautious operators.) Never interrupt the run for human-only work. Record it (record ... …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nousresearch/unbroker