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.
git 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/mcp/samihalawa/linkedin-godmode-plugin/linkedin-godmode)<a href="https://agentmods.dev/mcp/samihalawa/linkedin-godmode-plugin/linkedin-godmode"><img src="https://agentmods.dev/badge/mcp/samihalawa/linkedin-godmode-plugin/linkedin-godmode/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/mcp/samihalawa/linkedin-godmode-plugin/linkedin-godmode"><img src="https://agentmods.dev/badge/mcp/samihalawa/linkedin-godmode-plugin/linkedin-godmode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
linkedin-godmode 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 8d 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
{
"linkedin-godmode": {
"cwd": ".",
"command": "node",
"args": [
"./dist/cli.js",
"mcp"
]
}
}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.
- 8d ago First seen · 10 lines scan A f4e727c8b3ac
linkedin-godmode is an MCP server published in the GitHub repository samihalawa/linkedin-godmode-plugin (0 stars, last pushed 20d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
parallel-browser-mcp
MCP server for parallel browser automation across multiple providers. Runs locally from the parallel-browser-mcp npm package. Needs 7 environment variables to run.
sales-navigator
MCP server that gives AI assistants access to LinkedIn Sales Navigator contact and account search. Runs locally from the linkedin-sales-nav-mcp Python package.
linkedin-sales-nav-mcp
MCP server that gives AI assistants access to LinkedIn Sales Navigator contact and account search. Runs locally from the linkedin-sales-nav-mcp Python package.
curtis-mcp
Curtis is an MCP server that runs your LinkedIn outreach from your own machine: it logs in once, works through your contact list, and sends connection requests slowly enough to look like you. Runs locally from the curtis-mcp npm package.
linkedin-mcp
LinkedIn MCP server with auth and posting tools. Runs locally from the linkedin-mcp Python package.
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 2 environment variables to run.