Unbroker
Unbroker is a Hermes optional security skill for finding exposed personal information on data-broker / people-search sites and filing removals where possible. It is valuable, but it touches identity data, consent, email, broker forms, and compliance workflows, so Kevin's default route is review-first, approval-gated, and locally audited. Source: Hermes Agent docs, 2026-07-06
Source Snapshot
Official Hermes docs currently list Unbroker as:
| Field | Value |
|---|---|
| Source | Optional skill |
| Install | hermes skills install official/security/unbroker |
| Path | optional-skills/security/unbroker |
| Version | 1.0.0 |
| Author | SHL0MS |
| License | MIT |
| Platforms | Linux, macOS, Windows |
| Tags | privacy, data-broker, opt-out, CCPA, GDPR, security, doxxing |
Teknium's bookmarked launch note says the skill teaches Hermes to find personal data on data broker platforms and get it taken down. SHL0MS's launch framed it as open source and focused on finding exposed personal info and filing removals. The Hermes docs are the version authority. Source: X/@Teknium, 2026-07-03; X/@SHL0MS, 2026-07-03; Hermes docs, 2026-07-06
Safety Boundary
Unbroker should not run as an ordinary background automation in Kevin's stack. Before any live run:
- Record consent for each person whose data will be searched or removed.
- Review the exact personal fields being disclosed to brokers.
- Use a dedicated email/browser profile when possible.
- Log broker targets, submitted forms, sent emails, verification links, and human-only tasks.
- Do not bypass CAPTCHA, anti-bot gates, identity-proofing, phone calls, faxes, or government-ID checks.
- Confirm removals only after a follow-up scan verifies the listing is gone.
The docs describe an autonomy loop, but Kevin's local rule is stricter: privacy-sensitive workflows require explicit operator approval until a local audit proves the broker list, consent model, credentials, and reporting are acceptable.
Kevin Stack Route
Use Hermes Agent (Nous Research) as the runtime, Agent Security Model as the safety model, and Computer Use and Browser Automation Patterns for browser/form-driving boundaries. Keep Unbroker as a Hermes optional skill candidate, not a kevin-wiki executable skill, unless Kevin explicitly asks to install and audit it.
If adopted later, create a local wrapper skill that adds:
- consent intake and subject ledger
- environment/credential setup checklist
- dry-run mode
- broker-by-broker audit output
- human-task digest
- recurring rescan schedule
Timeline
- 2026-07-06 | Promoted the SHL0MS/Teknium Unbroker bookmark cluster into a focused Hermes optional-skill page with a safety boundary and version snapshot. Source: X bookmark artifact audit, 2026-07-06