linkedin-growth-config

linkedin-growth-config is a command for Claude Code from seaworld008/Commonly-used-high-value-skills. It costs 27 tokens per session (497 once invoked), scanned A, original, MIT.

A configuration command for changing how a LinkedIn lead pipeline handles accounts, invitations, pending requests, and lead qualification.

In plain words
What is it for?
Use it to change daily limits, invitation timing, retry rules, pending-request checks, account status, or the ideal customer profile.
Why use it?
It lets you adjust operating rules or pause an account without rebuilding the pipeline.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it to change daily limits, invitation timing, retry rules, pending-request checks, account status, or the ideal customer profile.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-config
Install

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.

Clone the repo
git clone --depth 1 https://github.com/seaworld008/Commonly-used-high-value-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for linkedin-growth-config

README.md
[![agentmods](https://agentmods.dev/badge/commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-config/github.svg)](https://agentmods.dev/commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-config)
Your own site
<a href="https://agentmods.dev/commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-config"><img src="https://agentmods.dev/badge/commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-config/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.

agentmods 80×15 button for linkedin-growth-config

Your own site · 80×15
<a href="https://agentmods.dev/commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-config"><img src="https://agentmods.dev/badge/commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 497 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00497
Opus 5 $0.00014 $0.00249
Sonnet 5 $0.00005 $0.00099
Haiku 4.5 $0.00003 $0.00050

Measured 9d ago against content hash b77e15001872, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

linkedin-growth-config 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 9d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

openclaw-skills/linkedin-growth/commands/linkedin-growth-config.md · 30 lines

What it actually says

Use the linkedin-growth skill to change configuration. Arguments: $ARGUMENTS

First show current state with node scripts/account.mjs list --json. Then apply what I asked, confirming the exact change back to me:

  • Daily invite limit (how many/day) → node scripts/account.mjs update --name <acct> --daily-invite-limit <n>
  • Invite pace (no more than one connect every N min) → node scripts/account.mjs update --name <acct> --min-invite-interval <n>
  • Active hours (when invites go out) → node scripts/account.mjs update --name <acct> --active-start <HH:MM> --active-end <HH:MM>
  • Pending threshold (check after N days) → node scripts/account.mjs update --name <acct> --max-pending-days <n>
  • Pending check batch per run → node scripts/account.mjs update --name <acct> --pending-batch-size <n>
  • Retry policy — if someone doesn't accept, try from other accounts (global, not per-account) → node scripts/settings.mjs set max_connect_attempts <1|N|all> (1 = no retry)
  • Temporarily stop an account → node scripts/account.mjs pause --name <acct> (and resume to re-enable). A paused account is skipped by both import round-robin and the scheduler.
  • Rename / remove an account → account.mjs rename / account.mjs remove
  • Change who we target (the ICP) → show me the current ICP with node scripts/settings.mjs get icp_definition, discuss the change, then save the new version with node scripts/settings.mjs set icp_definition --stdin (pipe via heredoc). It is stored in the database (not a file) and takes effect on the next import. The ICP is my own data, not a hardcoded list — don't leave stray ICP files around.

If I am vague, ask which account and which setting before changing anything. Never change limits or schedules without telling me the before/after values.

Changes

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.

  1. 9d ago First seen · 30 lines · 27 tokens per session scan A b77e15001872

Subscribe to this mod's changes

linkedin-growth-config is a command published in the GitHub repository seaworld008/Commonly-used-high-value-skills (70 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 497 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.