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.
npx agentmods add skills/itamarzand88/cli-anything-web/linkedin-clinpx skills add ItamarZand88/CLI-Anything-WEB --skill linkedin-cligit clone --depth 1 https://github.com/ItamarZand88/CLI-Anything-WEBWrote this? Show the measurements
A badge for your README with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them.
[](https://agentmods.dev/skills/itamarzand88/cli-anything-web/linkedin-cli)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 | $0.00093 | $0.00943 |
| Opus 5 | $0.00046 | $0.00472 |
| Sonnet 5 | $0.00019 | $0.00189 |
| Haiku 4.5 | $0.00009 | $0.00094 |
Grade A, and why
linkedin-cli 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cli-web-linkedin
Full LinkedIn client: search, profiles, feed, posting, reactions, comments, network, and messaging. All commands require auth login first.
Install: pip install "cli-web-linkedin[browser]", then playwright install chromium.
Commands
| Group | Commands |
|---|---|
search |
all|people|jobs|companies QUERY [--limit N] (default 10) |
profile |
me, get USERNAME |
feed |
feed [--count N] |
company |
company NAME (view page), company follow|unfollow COMPANY_URN |
jobs |
search QUERY [--limit N], get JOB_ID (full description) |
post |
create TEXT, edit POST_URN TEXT, delete POST_URN, react POST_URN [--type LIKE|PRAISE|EMPATHY|INTEREST|APPRECIATION|ENTERTAINMENT], unreact POST_URN, comment POST_URN TEXT, edit-comment COMMENT_URN TEXT, delete-comment COMMENT_URN |
notifications |
notifications [--limit N] |
network |
connections [--limit N], invitations [--limit N], accept|decline INVITATION_URN, connect PROFILE_URN [-m MESSAGE] |
messaging |
list [--limit N], read CONVERSATION_URN [--limit N], send RECIPIENT TEXT (conversation or profile URN) |
auth |
login, status, logout |
Examples
# Find people (returns name, headline, profile URL per result)
cli-web-linkedin search people "python developer" --limit 10 --json
# Job search, then full description
cli-web-linkedin jobs search "software engineer" --limit 5 --json
cli-web-linkedin jobs get 4388202530 --json
# Publish a post
cli-web-linkedin post create "Hello LinkedIn!" --json
# Pending invitations, then accept one (URN from the list)
cli-web-linkedin network invitations --json
cli-web-linkedin network accept "urn:li:invitation:123" --json
# Read recent messages
cli-web-linkedin messaging list --json
cli-web-linkedin messaging read "urn:li:msg_conversation:123" --json
JSON output
Every command accepts --json. Reads return the data object directly; writes return {"success": true, ...}. Errors return {"error": true, "code": "...", "message": "..."}.
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.
- 3d ago First seen · 71 lines · 93 tokens per session scan A eee3882e1afa
linkedin-cli is a skill published in the GitHub repository ItamarZand88/CLI-Anything-WEB (216 stars, last pushed 10d ago), licensed MIT. It adds 93 tokens to every session and 943 once invoked, about $0.0005 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-30.
Other skills, from other repositories
playwright-test-results
Query Playwright CI test results from the aggregated DuckDB database. Answers questions about flaky tests, failure rates, slow tests, and per-run/SHA/PR results without hunting through GitHub artifacts.
playwright-triage
Triage a Playwright bug report by reproducing it from the information in the issue. Use when asked to triage, reproduce, or verify a GitHub issue (a new bug report, or an existing report with a new comment).
playwright-dev
Explains how to develop Playwright - add APIs, MCP tools, CLI commands, and vendor dependencies.
copilotkit-setup
Use when adding CopilotKit to an existing project or bootstrapping a new CopilotKit project from scratch. Covers framework detection, package installation, runtime wiring (managed Intelligence or self-hosted SSE), provider setup, and first working chat integration.
a2ui-renderer
Render A2UI (Agent-to-UI declarative surfaces) in CopilotKit v2. Enable the runtime via CopilotRuntime({ a2ui: {...} }), then enable the provider via . Auto-activates via /info — do NOT manually pass renderActivityMessages. createA2UIMessageRenderer ships from @copilotkit/react-core/v2; low-level primitives…
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.