Have I Been Pwned

Operate Have I Been Pwned through your OOMOL-connected account. This skill calls the haveibeenpwned connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Have I Been Pwned. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "haveibeenpwned" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "haveibeenpwned" --action "<action_name>" --data '<json>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

• get_breach — Get one breach by its stable HIBP Name value.
• get_latest_breach — Get the most recently added breach in Have I Been Pwned.
• get_subscription_status — Get the current subscription details for the connected HIBP API key.
• list_breaches — List breaches in Have I Been Pwned and optionally filter by domain or spam-list flag.
• list_data_classes — List all data classes currently used by breaches in Have I Been Pwned.
• list_pastes_for_account — List paste exposures for an email address from Have I Been Pwned.
• search_breached_account — Search full HIBP breach models for an email address, with optional domain and unverified-breach filters.

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change Have I Been Pwned state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: ):

```bash

curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux

```

```powershell

irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell

```

• Not signed in / authentication error — sign in to your OOMOL account once:

```bash

oo auth login

```

• scope_missing / credential_expired / app_not_ready / app_not_found — Have I Been Pwned is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

```text

https://console.oomol.com/app-connections?provider=haveibeenpwned

```

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• Have I Been Pwned homepage: https://haveibeenpwned.com/