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 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 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/skills/itamarzand88/cli-anything-web/linkedin-cli)<a href="https://agentmods.dev/skills/itamarzand88/cli-anything-web/linkedin-cli"><img src="https://agentmods.dev/badge/skills/itamarzand88/cli-anything-web/linkedin-cli/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/skills/itamarzand88/cli-anything-web/linkedin-cli"><img src="https://agentmods.dev/badge/skills/itamarzand88/cli-anything-web/linkedin-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 37 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00093 | $0.00943 |
| Opus 5.5 | $0.00037 | $0.00377 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (234 stars, last pushed 5d ago), licensed MIT. It adds 93 tokens to every session and 943 once invoked, about $0.0004 per session on Opus 5.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
elnora-admin
This skill should be used when the user asks to "log in", "logout", "check auth", "create API key", "revoke API key", "list API keys", "check health", "submit feedback", "view audit log", "shell completions", "get account", "update account", "account details", "view agreements", "accept terms", "validate token"…
elnora-files
This skill should be used when the user asks to "list files", "read a file", "get file content", "view protocol output", "file versions", "version history", "download protocol", "upload file", "upload batch", "bulk upload", "create file", "archive file", "fork file", "promote file", "working copy", "commit working…
elnora-orgs
This skill should be used when the user asks to "list organizations", "create org", "org members", "billing", "invite member", "manage invitations", "list invitations", "resend invitation", "reinvite", "cancel invitation", "accept invitation", "get invitation info", "remove member from org", "organization library"…
elnora-platform
Use when the user asks about "Elnora platform", "elnora CLI", "platform API", "platform overview", "what commands are available", "elnora help", "how to use Elnora", or any general question about the Elnora AI Platform that doesn't fit a specific domain. Routes to domain-specific sub-skills for token-efficient…
elnora-tasks
This skill should be used when the user asks to "create a task", "send a message", "generate a protocol", "list tasks", "get task", "view task details", "read task messages", "update task status", "archive a task", "unarchive a task", "restore a task", "list archived tasks", "task attachments", "read an attachment"…
elnora-agent
This skill should be used when the user asks about "Elnora agent capabilities", "what can the agent do", "what tools does Elnora have", "what can Elnora do", "agent tools", "web search", "academic search", "PubMed", "ArXiv", "Exa", "Tavily", "Perplexity", "Valyu", "ToolUniverse", "scientific tools", "agent memory"…