linkedin-scraper

A tool for collecting information from LinkedIn profiles and company pages through Apify, a service that runs web-data collection programs.

In plain words
What is it for?
Use it to gather profile information, work history, and company data for prospecting, lead research, or sales preparation.
Why use it?
It reduces the need to open profiles and copy professional or company details manually.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add MSApps-Mobile/claude-plugins
agentmods
npx agentmods add plugins/msapps-mobile/claude-plugins/linkedin-scraper
Clone the repo
git clone --depth 1 https://github.com/MSApps-Mobile/claude-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

linkedin-scraper 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.

plugins/linkedin-scraper/.claude-plugin/plugin.json · 41 lines

What it actually says

{
  "name": "linkedin-scraper",
  "version": "0.2.0",
  "description": "Scrape LinkedIn profiles and company pages using Apify actors \u2014 extract professional data, work history, and company info without manual browsing.",
  "author": {
    "name": "MSApps",
    "email": "[email protected]"
  },
  "repository": "https://github.com/MSApps-Mobile/claude-plugins",
  "homepage": "https://github.com/MSApps-Mobile/claude-plugins/tree/main/plugins/linkedin-scraper",
  "license": "MIT",
  "privacy_policy": "https://opsagents.agency/privacy",
  "terms_of_service": "https://opsagents.agency/terms",
  "keywords": [
    "linkedin",
    "scraper",
    "apify",
    "sales",
    "leads",
    "profiles",
    "prospecting",
    "sosa-agents"
  ],
  "sosa": {
    "compliant": true,
    "level": 2,
    "impact": "medium",
    "methodology": "https://github.com/MSApps-Mobile/claude-plugins/blob/main/docs/SOSA.md",
    "whitepaper": "https://github.com/MSApps-Mobile/claude-plugins/blob/main/docs/sosa-whitepaper.pdf",
    "pillars": {
      "supervised": "User confirmation before scraping operations and data extraction",
      "orchestrated": "URL\u2192Scrape\u2192Parse\u2192Format pipeline with structured output",
      "secured": "Apify API token authentication, rate limiting, LinkedIn ToS awareness",
      "agents": "R=profile-extraction+company-intel, T=Apify API, M=LinkedIn data, P=scraping pipeline"
    }
  },
  "topics": [
    "sosa-agents"
  ]
}
Changes

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.

  1. yesterday First seen · 41 lines scan A ef8d1b4d31ea

Subscribe to this mod's changes

linkedin-scraper is a plugin published in the GitHub repository MSApps-Mobile/claude-plugins (9 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.