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 commands/rockyco/claude-linkedin-plugin/statusgit clone --depth 1 https://github.com/rockyco/claude-linkedin-pluginWrote 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/commands/rockyco/claude-linkedin-plugin/status)<a href="https://agentmods.dev/commands/rockyco/claude-linkedin-plugin/status"><img src="https://agentmods.dev/badge/commands/rockyco/claude-linkedin-plugin/status.svg" alt="Measured on agentmods" height="20"></a>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.00010 | $0.00153 |
| Opus 5 | $0.00005 | $0.00077 |
| Sonnet 5 | $0.00002 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
status 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 4d 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.
What it actually says
LinkedIn Status
Check the current LinkedIn authentication status.
Action
Run the auth check:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/linkedin-api.py check-auth
Also read ~/.claude/linkedin.local.md for the full settings.
Report to user
Tell the user:
- Whether they are authenticated
- Their display name and person URN
- How many days until the token expires
- If the token is expired, tell them to run
/linkedin:setupto re-authenticate
Do NOT display the access_token or client_secret values.
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.
- 4d ago First seen · 31 lines · 10 tokens per session scan A aa318b45c9ca
status is a command published in the GitHub repository rockyco/claude-linkedin-plugin (2 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 153 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.
Other commands, from other repositories
x-post
Draft (or take) a tweet/thread, optionally attach an image, score it against a built-in bookmarkability rubric, preview the cost, and post to X — ONLY after you explicitly confirm. Never auto-publishes. Can also SCHEDULE for later via vibedraft (single posts may carry one image or mp4 video; bulk is text-only)…
post
Compose and publish a post to X (Twitter).
setup
Set up X (Twitter) API authentication (OAuth 2.0 with PKCE).
status
Check X (Twitter) authentication status and token health.
Create a LinkedIn post from any content source.
all
Generate content for all platforms (X, LinkedIn, Medium, Dev.to) from a single input.