samihalawa/linkedin-godmode-plugin

LinkedIn-focused MCP server and CLI for local Chromium, Browserbase, and Anchor browser workflows

0Stars on the repository
6Mods indexed here, across every type
15d agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

samihalawa/linkedin-godmode-plugin

Skill Claude CodeCodex

Select and operate the local Playwright, Browserbase, or Anchor Browser provider for an authorized LinkedIn workflow. Use when session persistence, cloud browser attachment, provider profiles/contexts, or explicit hosted browser tasks matter.

not rated 0 15d ago A 48 tokens original MIT

samihalawa/linkedin-godmode-plugin

Skill Claude CodeCodex

Discover and replay current browser requests with generic network and HTTP tools. Use when an authorized LinkedIn workflow is more reliable through a captured request than fragile UI locators.

not rated 0 15d ago A 40 tokens original MIT

linkedin-operator

03

samihalawa/linkedin-godmode-plugin

Skill Claude CodeCodex

Operate the user's personal LinkedIn session with the plugin's generic browser and HTTP primitives. Use for authorized LinkedIn reading or changes when the caller must discover the current UI/request shape instead of relying on hardcoded business-action tools.

not rated 0 15d ago A 49 tokens original MIT

samihalawa/linkedin-godmode-plugin

Skill Claude CodeCodex

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.

not rated 0 15d ago A 44 tokens original MIT

samihalawa/linkedin-godmode-plugin

Skill Claude CodeCodex

Apply capture-first methodology to LinkedIn Voyager and SDUI traffic without hardcoding mutable endpoints. Use when interpreting captured LinkedIn web requests, query IDs, form state, decorations, or response shapes.

not rated 0 15d ago A 49 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: