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 skills/styfinity/linkedin-engine/linkedin-cold-revivernpx skills add styfinity/linkedin-engine --skill linkedin-cold-revivergit clone --depth 1 https://github.com/styfinity/linkedin-engineWhat 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 | $0.00044 | $0.00548 |
| Opus 5 | $0.00022 | $0.00274 |
| Sonnet 5 | $0.00009 | $0.00110 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
linkedin-cold-reviver 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Cold Reviver
A dying thread does not get revived by chasing. It gets revived by a new gift. This skill spots the cooling, then writes one revival message that is itself a value bomb.
Inputs
- The thread that has gone quiet (paste the full back-and-forth, with rough dates if you have them): $ARGUMENTS
- The brief (persona pains, offer, voice) loads automatically, so do not re-ask for context it already holds.
Do this
- Confirm it is actually cooling. Read the thread. Name the signal: a reply that trailed off, a "let me think", days of silence after warmth. If it is not cold yet, say so and stop.
- Find a brand-new angle. Do not reopen the old question. Pick a different pain, a different proof, or a different artefact tied to their world. One angle, not three.
- Build the value bomb. Write the message so the useful thing lands even if they never reply: a teardown, a specific number, a one-page resource, a stolen-with-pride tactic. They keep the value either way.
- Write the standalone CTA. It must work with zero memory of the prior thread. It names the artefact, states the one-word reply cost ("Reply 'send' and it's yours"), and names the outcome they get from it.
Output
- The revival message (the value bomb plus the standalone CTA), ready to read.
- A one-line note: why this angle is different from the one that went quiet.
- If they bite, hand the reply to /linkedin-reply-triager. Run /linkedin-humanizer on the draft before it ever sends.
Rules
- Never just re-ask the old question. A nag is not a revival.
- The value must land even if they bin you. If the message only works on a reply, rewrite it.
- One new angle, not a pile of follow-ups. No "just bumping this", no "did you see my last message".
- Draft only. Claude drafts, you approve, nothing sends without you. Sending happens only through the opt-in CLI/MCP layer wired to your own LinkedIn session or provider key, hard-capped at 20 actions/day for new accounts.
- No em-dashes. No guaranteed-result promises.
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.
- 2d ago First seen · 32 lines · 44 tokens per session scan A ab2ecfdfa562
linkedin-cold-reviver is a skill published in the GitHub repository styfinity/linkedin-engine (7 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 548 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
lemlist-campaign-from-icp
Use when the user says "create a lemlist campaign for X", "build a lemlist campaign from this ICP", "spin a lemlist campaign for Y", "ICP to lemlist", "natural language to lemlist campaign", "draft a lemlist campaign", "lemlist campaign for VPs/Managers/ICs at Z", or any variant indicating they want to turn a…
campaign-strategy
Pre-flight strategy advisor for a new campaign. Analyses every past campaign in the local YALC DB (HeyReach campaigns auto-sync on each run), their real outbound copy, where in the sequence each conversation first replied, every prior retro brief, and the validated/proven intelligence file. Then it proposes angle…
copywriting-follow-up
Writes follow-up cold emails after no reply from a prospect. Use this skill whenever the user wants to follow up on an email that got no response, says "write a follow-up", "they didn't reply, what do I send?", "draft a bump email", "write email 2 or 3 of my sequence", or asks how to re-engage a cold prospect. Works…
copywriting-ic-sequence
Writes a 3-email outbound sequence targeting Individual Contributors (SDR, AE, BDR, Account Manager, Marketing Specialist, Sales Rep, RevOps Analyst, CS Rep, etc.). Use this skill whenever the user wants to write cold emails for an IC, says "write me a sequence for SDRs", "draft emails targeting AEs", "emails for…
copywriting-manager-sequence
Writes a 3-email outbound sequence targeting Manager-level buyers (Sales Manager, Marketing Manager, RevOps Manager, Team Lead, Operations Manager, etc.). Use this skill whenever the user wants to write cold emails for a Manager, says "write me a sequence for a Sales Manager", "draft emails targeting managers", or…
copywriting-vp-sequence
Writes a 3-email outbound sequence targeting VP-level buyers (VP Sales, VP Marketing, VP Revenue, VP Operations, VP Product, etc.). Use this skill whenever the user wants to write cold emails for a VP, says "write me a sequence for a VP of Sales", "draft emails targeting VP-level", or provides a VP persona and asks…