linkedin-research

linkedin-research is a command for Claude Code from ketankhairnar/ai-sales-team-public. It costs 32 tokens per session (3,083 once invoked), scanned A, original, MIT.

A command that collects and analyzes information from a LinkedIn profile for basalt-research intake. It gathers the profile, activity, and articles, then produces structured notes.

In plain words
What is it for?
Researching a LinkedIn prospect, saving raw profile data, and creating intake notes with a two-pass analysis process.
Why use it?
It turns a profile URL into an organized research record and checks whether existing collected data should be reused or refreshed.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/ketankhairnar/Desktop/AIC.

Good fit Researching a LinkedIn prospect, saving raw profile data, and creating intake notes with a two-pass analysis process.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code.

Wrote 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.

agentmods badge for linkedin-research

README.md
[![agentmods](https://agentmods.dev/badge/commands/ketankhairnar/ai-sales-team-public/linkedin-research/github.svg)](https://agentmods.dev/commands/ketankhairnar/ai-sales-team-public/linkedin-research)
Your own site
<a href="https://agentmods.dev/commands/ketankhairnar/ai-sales-team-public/linkedin-research"><img src="https://agentmods.dev/badge/commands/ketankhairnar/ai-sales-team-public/linkedin-research/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.

agentmods 80×15 button for linkedin-research

Your own site · 80×15
<a href="https://agentmods.dev/commands/ketankhairnar/ai-sales-team-public/linkedin-research"><img src="https://agentmods.dev/badge/commands/ketankhairnar/ai-sales-team-public/linkedin-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,083 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.03083
Opus 5 $0.00016 $0.01541
Sonnet 5 $0.00006 $0.00617
Haiku 4.5 $0.00003 $0.00308

Measured 12d ago against content hash 6d86bfcad3e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

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

commands/linkedin-research.md · 335 lines

How it starts

The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.

linkedin-research — LinkedIn Profile Intelligence


Step 1: Parse & Setup

  1. Extract the LinkedIn profile URL from $ARGUMENTS (strip whitespace).
  2. Extract the slug from the URL: split on /in/, take the part after it, strip trailing / and query params. Example: https://www.linkedin.com/in/some-person/some-person.
  3. Set paths:
    • PROSPECT_DIR = prospects/{slug}/
    • RAW_DATA = prospects/{slug}/linkedin_raw_data.json
    • OUTPUT = prospects/{slug}/notes/linkedin-intake.md
    • COOKIES = plugins/linkedin-research/.cookies.json
    • SCRAPER = plugins/linkedin-research/linkedin-research.py
  4. Create directories: prospects/{slug}/notes/ (use mkdir -p).

IMPORTANT: Before running the scraper, check if linkedin_raw_data.json already exists at the output path. If it does, ask the user:

"linkedin_raw_data.json already exists for {slug}. Use existing data or re-scrape?" If they say use existing, skip Step 2 entirely.


Step 2: Run Scraper

Run the Playwright scraper via Bash:

cd /Users/ketankhairnar/Desktop/AIC && python plugins/linkedin-research/linkedin-research.py {profile_url} {RAW_DATA} --cookies {COOKIES}
  • If exit code != 0, show the error and STOP. Do not proceed with missing data.
  • If successful, read linkedin_raw_data.json and report:
✓ Scraper complete
  Profile: {meta.profile_text_length} chars
  Activity: {meta.activity_text_length} chars
  Articles: {meta.articles_text_length} chars
  Status: {scrape_status summary}

Step 3: Read Raw Data

Read the full linkedin_raw_data.json into context. You need ALL of it for the analysis passes.

DATA QUALITY GATE: Check meta.scrape_status and text lengths:

  • If profile_text_length < 200 or scrape_status.profile is "failed" or "suspicious": STOP and tell the user "Scraper returned insufficient profile data — likely auth issue, private profile, or CAPTCHA. Re-export cookies: python plugins/linkedin-research/linkedin-research.py --export-cookies plugins/linkedin-research/.cookies.json"
  • If activity_text_length < 100: Note "No activity data — this person may not post on LinkedIn. Analysis will rely on profile data only."
  • If articles_text_length < 100: Note "No published articles found."

Read the full file on GitHub · 335 lines

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. 12d ago First seen · 335 lines · 32 tokens per session scan A 6d86bfcad3e6

Subscribe to this mod's changes

linkedin-research is a command published in the GitHub repository ketankhairnar/ai-sales-team-public (2 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 3,083 once invoked, about $0.0002 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.