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-config)<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.
<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>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.00027 | $0.00497 |
| Opus 5.5 | $0.00011 | $0.00199 |
| Sonnet 5.5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00050 |
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 1mo 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-config — 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 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>(andresumeto 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 withnode 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.
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.
- 1mo ago First seen · 30 lines · 27 tokens per session scan A b77e15001872
linkedin-growth-config is a command published in the GitHub repository seaworld008/Commonly-used-high-value-skills (73 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 497 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to linkedin-growth-config, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
verify-custom-rules
Verify custom rules for Safety Net.
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.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.