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.
git clone --depth 1 https://github.com/seaworld008/Commonly-used-high-value-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/seaworld008/commonly-used-high-value-skills/linkedin-growth-setup)<a href="https://agentmods.dev/commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-setup"><img src="https://agentmods.dev/badge/commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-setup/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/commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-setup"><img src="https://agentmods.dev/badge/commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-setup.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.00843 |
| Opus 5 | $0.00012 | $0.00421 |
| Sonnet 5 | $0.00005 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
linkedin-growth-setup 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- linkedin-growth-setup — 100% identical, 0 lines differ
What it actually says
Use the linkedin-growth skill. Walk me through first-run setup, doing as much as possible yourself and only asking me for things you genuinely cannot obtain (LinkedIn tokens, account names, preferred invite limits/times).
Follow the skill's "First-run setup" section end to end:
- Verify Node ≥ 20. If missing, give me the exact install command for my OS and stop.
- From the skill directory run
node scripts/doctor.mjs --json. If dependencies are missing, runnpm install --omit=devand re-check. - For each failing check, apply the documented remediation:
- install
linkedin-cliif absent - if no LinkedIn accounts are connected, ask me for my Linked API Token and
Identification Token (from app.linkedapi.io) and run
linkedin setup ...per account - register each connected account into the DB with
node scripts/account.mjs add, asking me for a short name, a daily invite limit, and the daily hours during which invites should go out (--active-start/--active-end, e.g. 09:00–18:00). If I have more than one account, suggest slightly different hours so they don't act at the exact same time.
- install
- Ask me ONCE about the pace between connection requests (not per account): "By default
each account sends at most one connection request every 15 minutes — keep 15, or change
it?". Apply my answer to ALL accounts via
--min-invite-interval <N>(pass it on eachaccount.mjs add, oraccount.mjs updatethem afterward). Tell me I can fine-tune this per account later just by asking — e.g. "make kiril send one every 30 minutes". - Re-run the doctor until
"ok": true. - Ask me about the retry policy: "If someone doesn't accept the request, should we try
connecting from another account?" — then set it with
node scripts/settings.mjs set max_connect_attempts <1|N|all>(default 1 = no retry). - Once at least one account is registered, turn on the background scheduler with
node scripts/schedule.mjs installand confirm withnode scripts/schedule.mjs status.
Then summarize in plain language: which accounts are connected, how many invites per day each sends, during which hours, and at what pace (one every N minutes), the retry policy, and that the pipeline now runs in the background on its own. Do NOT mention internal scheduling details (wake-up intervals, ticks). Do not send any invites during setup.
- Optionally capture my ICP now so the first import is smooth. Ask who my ideal leads are
and who to filter out — roles/seniority, industries/company types, company size/stage,
locations to include/exclude, and any hard exclusions. Summarize it back, then save with
node scripts/settings.mjs set icp_definition --stdin(pipe the agreed text in via a heredoc — it is stored in the database, not a file; do not leave stray ICP files around). If I'd rather decide later, skip this — the import flow will ask before qualifying.
Finally — and this is required — give me the next step and offer to do it now. Setup
alone imports nothing; the pipeline stays empty until leads are added. Say something like:
"To start filling the pipeline, send me a LinkedIn or Sales Navigator search URL (or search
filters) plus a name for the list, and I'll import and qualify your first batch." If I give
you one, continue straight into the import (the /linkedin-growth-import flow). Never end the setup
without offering this next step.
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.
- 8d ago First seen · 53 lines · 23 tokens per session scan A 84170ffbffd4
linkedin-growth-setup is a command published in the GitHub repository seaworld008/Commonly-used-high-value-skills (70 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 843 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-09-03.
Other commands, from other repositories
audit-accessibility
Audit web page or component for WCAG accessibility compliance.
setup
Diagnose-first project setup with state machine — scans, confirms, interviews, writes.
update-docs
Sync documentation from source-of-truth files such as scripts, schemas, routes, and exports.
diagram-from-url
Generate educational diagram from a URL source using Excalidraw.
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.