linkedin-intel:post

linkedin-intel:post is a command for Claude Code from ketankhairnar/ai-sales-team-public. It costs 26 tokens per session (1,710 once invoked), scanned A, original, MIT.

A command for analysing one LinkedIn post, including its engagement, comments, audience, and topics.

In plain words
What is it for?
Use it to extract the post’s activity ID, collect its data, and produce a written analysis.
Why use it?
It brings the post’s main signals into one report instead of requiring separate manual review.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths.

Good fit Use it to extract the post’s activity ID, collect its data, and produce a written analysis.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ketankhairnar/ai-sales-team-public/linkedin-intel-post
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.

Clone the repo
git clone --depth 1 https://github.com/ketankhairnar/ai-sales-team-public

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-intel:post

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/ketankhairnar/ai-sales-team-public/linkedin-intel-post"><img src="https://agentmods.dev/badge/commands/ketankhairnar/ai-sales-team-public/linkedin-intel-post.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,710 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.00026 $0.01710
Opus 5 $0.00013 $0.00855
Sonnet 5 $0.00005 $0.00342
Haiku 4.5 $0.00003 $0.00171

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

Security

Grade A, and why

linkedin-intel:post 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 11d 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-intel:post.md · 214 lines

How it starts

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

linkedin-intel:post — LinkedIn Post Intelligence


Step 0: Load Interpretive Lens

Read ~/.claude/skills/linkedin-intel/SKILL.md into context using the Read tool. Apply its principles (signal hierarchy, extraction rules, topic extraction, confidence calibration, data quality gates) throughout all analysis steps below.


Step 1: Parse & Setup

  1. Extract the LinkedIn post URL from $ARGUMENTS (strip whitespace).
  2. Extract the activity ID from the URL: match the regex activity[:\-](\d{19,20}) and take the numeric capture group. Examples:
    • https://www.linkedin.com/feed/update/urn:li:activity:7654321098765432100/ -> 7654321098765432100
    • https://www.linkedin.com/posts/some-slug_topic-activity-7654321098765432100-xxxx -> 7654321098765432100
  3. Set paths:
    • SCRAPER = ~/Desktop/AIC/plugins/linkedin-intel/linkedin-scraper.py
    • COOKIES = ~/Desktop/AIC/plugins/linkedin-intel/.cookies.json
    • RAW_DATA = ~/Desktop/AIC/linkedin/posts/{activity-id}/linkedin_raw_data.json
    • OUTPUT = ~/Desktop/AIC/linkedin/posts/{activity-id}/notes/post-report.md
  4. Create directories: ~/Desktop/AIC/linkedin/posts/{activity-id}/notes/ (use mkdir -p).

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

"linkedin_raw_data.json already exists for activity {activity-id}. 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 ~/Desktop/AIC/plugins/linkedin-intel && python linkedin-scraper.py --mode post {post_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:

Read the full file on GitHub · 214 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. 11d ago First seen · 214 lines · 26 tokens per session scan A 38f97b82c0d9

Subscribe to this mod's changes

linkedin-intel:post is a command published in the GitHub repository ketankhairnar/ai-sales-team-public (2 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 1,710 once invoked, about $0.0001 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.