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-import)<a href="https://agentmods.dev/commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-import"><img src="https://agentmods.dev/badge/commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-import/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-import"><img src="https://agentmods.dev/badge/commands/seaworld008/commonly-used-high-value-skills/linkedin-growth-import.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.00032 | $0.00725 |
| Opus 5.5 | $0.00013 | $0.00290 |
| Sonnet 5.5 | $0.00006 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
linkedin-growth-import 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-import — 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 run a Phase A import. Arguments: $ARGUMENTS
Drive the full import flow:
- Determine the inputs. If I gave a search URL, detect the type (URL containing
/sales/→nv, otherwisest). If I gave filters instead, use them. Ask me for anything missing: which account should run the search (--searcher), and a list name (--list). If I have more than one account, confirm the searcher with me. - Always ask me the limit — how many of the found leads to take. I can give a number or say "max" for the maximum (Sales Navigator caps at 2500, standard search at 1000). Do not assume a default; this question is required every time.
- Run
node scripts/import.mjs prepare --searcher <acct> --list "<name>" --type <nv|st> --limit <N|max>with either--search-url "<url>"or the filter flags. (--limitis required; a number above the cap is clamped and reported aslimit_capped_to_max.) - Settle the ICP before qualifying (this is the filtering step — make it explicit, not
silent). The
prepareoutput tells you whether an ICP is configured:- If none is configured, interview me: which roles/seniority to target, which
industries/company types fit, company size/stage if relevant, locations to include or
exclude, and any hard exclusions. Summarize what you heard, then save it with
node scripts/settings.mjs set icp_definition --stdin(pipe the text via a heredoc — it is stored in the database, not a file; do not leave stray ICP files in the repo or tmp). - If one is configured, show it to me in plain language and ask whether to use it as-is or adjust it for this list (re-save if I change it).
- If none is configured, interview me: which roles/seniority to target, which
industries/company types fit, company size/stage if relevant, locations to include or
exclude, and any hard exclusions. Summarize what you heard, then save it with
- Read the returned candidate file and qualify every candidate against my ICP, using the
output contract in
config/qualification-prompt.md. For more than ~25 candidates, chunk the work and delegate each chunk to a sub-agent. Use a cheap/fast model for these qualification sub-agents — it's simple classification, not deep reasoning (in Claude Code, spawn them withmodel: "haiku"; in other hosts use their small/fast model). Keep orchestration on the main model. Produce a JSON array[{hashed_url, suitable, reasoning}]covering every candidate (reasoning must cite the ICP criterion that drove the decision), and write it to the expected result file path. - Run
node scripts/import.mjs commit --batch <id> --results <file>. - Report transparently: how many were found, skipped as duplicates, kept vs filtered, a few concrete sample reasons from both sides, and how the new leads were distributed across accounts.
Never send invites here — import only stores leads as not_connected.
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 · 43 lines · 32 tokens per session scan A 28ff2dbf24ec
linkedin-growth-import is a command published in the GitHub repository seaworld008/Commonly-used-high-value-skills (73 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 725 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-import, 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.