Borrowing it
Nothing to install: this file belongs to MCPWorks-Technologies-Inc/linkedin-pages-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/MCPWorks-Technologies-Inc/linkedin-pages-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/MCPWorks-Technologies-Inc/linkedin-pages-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/mcpworks-technologies-inc/linkedin-pages-mcp/claude-md)<a href="https://agentmods.dev/instructions/mcpworks-technologies-inc/linkedin-pages-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/mcpworks-technologies-inc/linkedin-pages-mcp/claude-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/mcpworks-technologies-inc/linkedin-pages-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/mcpworks-technologies-inc/linkedin-pages-mcp/claude-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.00377 | $0.00377 |
| Opus 5 | $0.00188 | $0.00188 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
linkedin-pages-mcp CLAUDE.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 12d 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
CLAUDE.md — linkedin-pages-mcp
MCP server for LinkedIn Company Page management via the official Community Management API. MIT licensed.
Commands
pip install -e ".[dev]" # Install with dev deps
pytest tests/ -v # Run tests
black src/ tests/ # Format
ruff check src/ tests/ # Lint
mypy src/ # Type check
Run
export LINKEDIN_ACCESS_TOKEN="ya29.xxx"
export LINKEDIN_ORGANIZATION_ID="111806031"
linkedin-pages-mcp # stdio mode
python -m linkedin_pages_mcp # alternative
Structure
src/linkedin_pages_mcp/
__init__.py # Version
__main__.py # Entry point
client.py # LinkedIn API HTTP client
server.py # MCP server + tool definitions
LinkedIn API
- Base:
https://api.linkedin.com/rest - Auth: OAuth 2.0 bearer token (3-legged, user must be page admin)
- Version header:
LinkedIn-Version: 202503 - Docs: https://learn.microsoft.com/en-us/linkedin/marketing/community-management/
Tools (16)
Posts: create, list, get, update, delete Comments: list, create, delete Reactions: list, add Analytics: follower stats, page stats, post stats, follower demographics Media: initialize image upload Organization: get company details
Do NOT
- Store LinkedIn member data beyond 48 hours (API policy)
- Auto-post without user intent (spam risk, ToS violation)
- Use unofficial/scraping libraries (this uses the official API only)
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.
- 12d ago First seen · 55 lines · 377 tokens per session scan A 0472cdd54c01
linkedin-pages-mcp CLAUDE.md is an instructions file published in the GitHub repository MCPWorks-Technologies-Inc/linkedin-pages-mcp (1 stars, last pushed 5mo ago), licensed MIT. It adds 377 tokens to every session, about $0.0019 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).