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 instructions/bcharleson/linkedincli/claude-mdgit clone --depth 1 https://github.com/bcharleson/linkedincliWhat 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.00806 | $0.00806 |
| Opus 5 | $0.00403 | $0.00403 |
| Sonnet 5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
linkedincli CLAUDE.md 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 2d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
linkedin-cli
CLI and MCP server for LinkedIn — full platform management via cookie session auth (Voyager API).
Architecture
Single source of truth: Every LinkedIn API endpoint is one CommandDefinition object that powers both the CLI (Commander.js) and MCP server simultaneously.
src/
├── index.ts # CLI entry (Commander.js)
├── mcp.ts # MCP server entry (stdio)
├── core/
│ ├── types.ts # CommandDefinition, LinkedInClient interfaces
│ ├── client.ts # HTTP client (Voyager API, cookie auth, retry)
│ ├── handler.ts # executeCommand() — builds requests from definitions
│ ├── auth.ts # resolveAuth() — flag > env > config file
│ ├── config.ts # ~/.linkedin-cli/config.json manager
│ ├── errors.ts # Typed error classes
│ └── output.ts # JSON formatting, --fields, --quiet
├── commands/
│ ├── index.ts # allCommands registry + registerAllCommands()
│ ├── auth/login.ts # login, logout, status (special commands)
│ ├── mcp/index.ts # MCP start command
│ ├── profile/view.ts # 9 profile commands
│ ├── posts/create.ts # 3 post commands (create, edit, delete)
│ ├── feed/feed.ts # 3 feed commands (view, user, company)
│ ├── engage/engage.ts # 5 engagement commands (react, comment, share)
│ ├── connections/ # 7 connection commands
│ ├── messaging/ # 6 messaging commands
│ ├── search/search.ts # 4 search commands (people, companies, jobs, posts)
│ ├── companies/ # 3 company commands
│ ├── jobs/jobs.ts # 2 job commands
│ └── analytics/ # 1 analytics command
└── mcp/
└── server.ts # MCP server registration loop
Authentication
Cookie-based auth via LinkedIn's Voyager API. Two cookies required:
li_at— main session tokenJSESSIONID— session ID (used for CSRF token)
Resolution order: --li-at/--jsessionid flags → LINKEDIN_LI_AT/LINKEDIN_JSESSIONID env vars → ~/.linkedin-cli/config.json
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.
- 2d ago First seen · 74 lines · 806 tokens per session scan A b55dc72948bc
linkedincli CLAUDE.md is an instructions file published in the GitHub repository bcharleson/linkedincli (56 stars, last pushed 10d ago), licensed MIT. It adds 806 tokens to every session, about $0.0040 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.