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/linked-api/linkedin-skills/linkedin-growth-statusgit clone --depth 1 https://github.com/Linked-API/linkedin-skillsWrote 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/linked-api/linkedin-skills/linkedin-growth-status)<a href="https://agentmods.dev/commands/linked-api/linkedin-skills/linkedin-growth-status"><img src="https://agentmods.dev/badge/commands/linked-api/linkedin-skills/linkedin-growth-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.1 | $0.00028 | $0.00291 |
| Opus 5 | $0.00014 | $0.00146 |
| Sonnet 5 | $0.00006 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
linkedin-growth-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 6d 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.
This is a copy
100% identical to linkedin-growth-status — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Use the linkedin-growth skill to answer status questions. Arguments: $ARGUMENTS
- Start with the dashboard:
node scripts/status.mjs --json(add--account <name>if I named one, and--since 7d/30dif I asked about a time window). - Present it clearly per account: paused?, daily limit, invites sent today and remaining, counts by status (not_connected / pending / connected / withdrawn / error), and any recent errors.
- If I asked something the dashboard does not directly answer (conversion rates, best
lists, pending older than N days, per-list breakdowns), consult
node scripts/schema.mjs --examples --jsonand then run a read-only query withnode scripts/query.mjs --sql "..." --json. - For a specific lead, use
node scripts/lead.mjs show "<name|url>" --jsonand explain its status and recent run history.
These reads hit the local database (fast, free). Only if I explicitly ask for the live LinkedIn state should you call linkedin-cli directly.
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.
- 6d ago First seen · 22 lines · 28 tokens per session scan A 394c3094d631
linkedin-growth-status is a command published in the GitHub repository Linked-API/linkedin-skills (50 stars, last pushed 24d ago), licensed MIT. It adds 28 tokens to every session and 291 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to linkedin-growth-status, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
cancel-ralph
Cancel active Ralph Loop.
release
Git geçmişinden hedef kitleye uygun sürüm notları oluştur.
spec-forge
Use when generating software specifications — full chain (Idea→Decompose→Tech Design + Feature Specs) or individual documents.
dd-init
Initialize product documentation structure in current directory.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.