Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add samihalawa/linkedin-godmode-plugin --skill linkedin-safety-verificationgit clone --depth 1 https://github.com/samihalawa/linkedin-godmode-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/samihalawa/linkedin-godmode-plugin/linkedin-safety-verification)<a href="https://agentmods.dev/skills/samihalawa/linkedin-godmode-plugin/linkedin-safety-verification"><img src="https://agentmods.dev/badge/skills/samihalawa/linkedin-godmode-plugin/linkedin-safety-verification/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/samihalawa/linkedin-godmode-plugin/linkedin-safety-verification"><img src="https://agentmods.dev/badge/skills/samihalawa/linkedin-godmode-plugin/linkedin-safety-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00044 | $0.00424 |
| Opus 5 | $0.00022 | $0.00212 |
| Sonnet 5 | $0.00009 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
linkedin-safety-verification scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Safety and verification
- 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.
- Prefer
LINKEDIN_GODMODE_READ_ONLY=1for inspection. - Keep capture scope narrow; bodies are opt-in.
- Never expose cookies, authorization, API keys, CDP URLs, or task secrets.
- 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.
- 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.
- 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.
- 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.
- Verify the failing or changed layer itself: browser state for UI, fresh API read for HTTP, provider status for hosted tasks.
- 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.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 20 lines · 44 tokens per session scan A 64eee2a6ae00
linkedin-safety-verification is a skill published in the GitHub repository samihalawa/linkedin-godmode-plugin (0 stars, last pushed 21d ago), licensed MIT. It adds 44 tokens to every session and 424 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
job-search
Search LinkedIn, Hacker News, and Twitter/X for jobs with connections, hiring manager insights, and preference-based scoring. Use when the user wants to find jobs, search for positions, or explore job opportunities.
job-preferences
Set or update job-search preferences such as titles, salary, remote work, and filters for the other Job Apply skills.
mk:agent-browser
Browser automation CLI for AI agents using agent-browser. Use for navigating websites, clicking/filling pages, screenshots, data extraction, web app testing, exploratory QA, dogfooding, Electron apps, Slack automation, Vercel Sandbox browser runs, AWS AgentCore cloud browsers, auth-heavy flows, and long autonomous…
linkedin-outreach
Playbook for using the Curtis server — preparing the contact list, writing the messages, reading the right numbers, and repairing selectors when LinkedIn changes the DOM. Use it when the user wants to send connection requests or messages on LinkedIn with this tool.
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.