---
name: linkedin-safety-verification
description: Apply security, read-only, authorization, and same-layer verification rules to agent-operated LinkedIn workflows. Use before account-visible changes, private request replay, broad captures, or provider AI tasks.
---

# Safety and verification

1. Establish from the current request and authenticated account context that the user controls the account and requested the operation. Do this once for batch scope. Standing authorization eliminates agent-invented gates but never overrides the selected controller's action-time confirmation policy for sensitive-data entry, uploads, or submission.
2. Prefer `LINKEDIN_GODMODE_READ_ONLY=1` for inspection.
3. Keep capture scope narrow; bodies are opt-in.
4. Never expose cookies, authorization, API keys, CDP URLs, or task secrets.
5. Bulk work is allowed when the user authorizes the cohort, filters, or all matching items. Do not bypass challenges, evade limits, import/export cookies, schedule unrequested recurring campaigns, or add hidden out-of-scope loops.
6. Use the user-selected authenticated controller as authoritative. One controller's failure does not prove LinkedIn unavailable, and concurrent controllers must not read or write the same LinkedIn account.
7. For each write, execute once, verify it, and continue automatically. If the selected controller mandates action-time confirmation, prepare as far as allowed and ask once at the latest permitted moment with the exact role, destination, data, file, and action. Group only fully defined imminent actions; never ask early, vaguely, or again for an unchanged disclosed action.
8. After one literal account-wide quota or restriction state, preserve the queue and use independent authorized routes; recheck the blocked lane only after a reset or state-change signal.
9. Verify the failing or changed layer itself: browser state for UI, fresh API read for HTTP, provider status for hosted tasks.
10. State exact uncertainty when cloud providers or live LinkedIn behavior were not exercised. Do not infer exclusive causality from missing logs.

Use `references/verification-gates.md` for preflight and closure checks.