Borrowing it
Nothing to install: this file belongs to devag7/linkedin-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/devag7/linkedin-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/devag7/linkedin-mcpWrote 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/instructions/devag7/linkedin-mcp/agents-md)<a href="https://agentmods.dev/instructions/devag7/linkedin-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/devag7/linkedin-mcp/agents-md/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/instructions/devag7/linkedin-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/devag7/linkedin-mcp/agents-md.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.00809 | $0.00809 |
| Opus 5.5 | $0.00324 | $0.00324 |
| Sonnet 5.5 | $0.00162 | $0.00162 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
linkedin-mcp AGENTS.md 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI agents using or contributing to LinkedIn MCP
(linkedin-mcp-tools).
What this is
An MCP server exposing LinkedIn to any MCP client (Claude, Cursor, …) as structured JSON. It drives a real stealth Chrome to pass Cloudflare, then calls LinkedIn's Voyager API from inside the authenticated page. Source 4.2.0 has 24 tools, including two offline job-seeker tools introduced in 4.1.0. The earlier 4.0.0 had 22; publication is tracked in the version's release evidence.
Using it (as an agent / MCP client)
- The human runs the one-time login:
npx -y linkedin-mcp-tools@latest --login. - Configure the MCP server: command
npx, args["-y","linkedin-mcp-tools@latest"]. - Call tools. Reads return structured JSON. Writes are disabled by default. After deliberate runtime opt-in, preview
with confirmation omitted/false, obtain explicit human approval, then submit
identical action/target/content with
confirm: true, returnedoperation_idand five-minutepreview_token. The server cannot infer human consent. Writes count against daily safety caps — only call them when the user explicitly asks, and surface the returnedstatus(ok/duplicate/already_connected/restricted/quota_exhausted/not_allowed/failed/unknown) back to the user. - Use cold
whoamior offline--doctorfor local diagnosis.health_checkmakes a live account read; call it only within the authorized scope and request budget. Stop at checkpoints rather than adding probes or retries.
Tool map
- Profiles:
get_my_profile,get_profile - Search:
search_people,search_jobs,get_job_details,search_companies,get_company,get_company_posts,get_company_employees,prepare_job_application,export_application_tracker(published local preparation/export; optional reusable evidence and draft materials; neither submits or stores applications) - Feed/messaging:
get_feed,get_notifications,get_inbox,get_conversation,get_pending_invitations - Writes (gated):
connect_with_person,send_message,create_post,react_to_post,comment_on_post - Session:
whoami,health_check,close_session
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.
- yesterday Changed · +7 tokens per session dbb87610d0e0
- 2d ago Changed · -1 tokens per session a4aceeb671be
- 7d ago Changed · +1 lines · +18 tokens per session 12c43d562048
- 10d ago Changed · +4 tokens per session 1b40342fdf94
- 11d ago Changed · +3 lines · +50 tokens per session a0da63d23e04
- 17d ago Changed c022c0278900
- 27d ago Changed · +9 lines · +149 tokens per session 748c743314f1
- 1mo ago First seen · 49 lines · 582 tokens per session scan A 07abe4be1a9f
linkedin-mcp AGENTS.md is an instructions file published in the GitHub repository devag7/linkedin-mcp (12 stars, last pushed 2d ago), licensed MIT. It adds 809 tokens to every session, about $0.0032 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.