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-sell-by-chatnpx skills add styfinity/linkedin-engine --skill linkedin-sell-by-chatgit clone --depth 1 https://github.com/styfinity/linkedin-engineWrote 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/skills/styfinity/linkedin-engine/linkedin-sell-by-chat)<a href="https://agentmods.dev/skills/styfinity/linkedin-engine/linkedin-sell-by-chat"><img src="https://agentmods.dev/badge/skills/styfinity/linkedin-engine/linkedin-sell-by-chat.svg" alt="Measured on agentmods" 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 | $0.00056 | $0.00565 |
| Opus 5 | $0.00028 | $0.00282 |
| Sonnet 5 | $0.00011 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
linkedin-sell-by-chat 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 4d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Sell By Chat
The hero outreach skill. Selling on LinkedIn is a six-stage conversation, not a pitch. This skill reads where the thread actually is and drafts only the next message, so you never run ahead of the buyer.
Inputs
- The conversation so far, pasted in full, plus the offer: $ARGUMENTS
- The brief (offer, pains, voice profile) loads automatically.
Do this
- Read the thread and identify which of the six stages it is at right now. The six stages:
- Open on their world, not your offer. A genuine, specific opener about them.
- One real insight that earns the reply. Useful on its own, no ask attached.
- Qualify the problem, message one: confirm the problem actually exists for them.
- Qualify the problem, message two: confirm the problem actually hurts.
- Introduce the offer, ONLY after they have confirmed the problem exists.
- Send the calendar link, ONLY after they say yes to a call.
- Draft only the next single message for the stage they are at. One message, not a sequence.
- Never skip a stage. Never pitch before the problem is confirmed (stages 3 and 4). Never send the link before a clear yes (stage 6).
- If the thread is ambiguous, name the most likely stage, say why, and draft for that one.
Output
- The next message, ready to copy.
- The stage it belongs to (1 to 6).
- What a yes vs a no looks like at this stage, so the user knows whether to advance or hold.
Rules
- One message at a time. Never draft ahead of the buyer.
- Gate the offer behind problem-confirmation, and the link behind an explicit yes.
- Once they say yes, stop selling and book. Hand to /linkedin-booking-closer.
- Run /linkedin-humanizer on the draft if it reads stiff.
- Draft only. Claude drafts, the operator approves and sends. Sending happens only through the connected CLI/MCP layer, wired to your own LinkedIn session or provider key, hard-capped at 20 actions per day for new accounts.
- No em-dashes. No guaranteed-result or "10x in a week" 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.
- 4d ago First seen · 39 lines · 56 tokens per session scan A 17221b657f2c
linkedin-sell-by-chat is a skill published in the GitHub repository styfinity/linkedin-engine (7 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 565 once invoked, about $0.0003 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
LinkedIn Automation
Automate LinkedIn marketing, lead generation, content publishing, and professional networking.
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…