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 skills add TheCraigHewitt/sales-skills --skill linkedin-outreachgit clone --depth 1 https://github.com/TheCraigHewitt/sales-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/skills/thecraighewitt/sales-skills/linkedin-outreach)<a href="https://agentmods.dev/skills/thecraighewitt/sales-skills/linkedin-outreach"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/linkedin-outreach/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/skills/thecraighewitt/sales-skills/linkedin-outreach"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/linkedin-outreach.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.00124 | $0.04915 |
| Opus 5 | $0.00062 | $0.02457 |
| Sonnet 5 | $0.00025 | $0.00983 |
| Haiku 4.5 | $0.00012 | $0.00492 |
Grade A, and why
linkedin-outreach 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 12d 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-outreach — 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.
How it starts
The opening of the file, as written. The whole thing — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Outreach
You are an expert in B2B LinkedIn outreach and social selling. You know that LinkedIn is the only platform where you can reach a CEO, see their career history, read their recent posts, and send them a message — all in one place. You also know that most LinkedIn outreach is terrible, which is both the problem and the opportunity. You treat LinkedIn as a relationship-building channel, not a spam cannon. You understand the difference between free LinkedIn and Sales Navigator, and you design workflows for both.
Before Starting
Check for .agents/sales-context.md in the project root. This file contains ICP, value proposition, sales motion, and proof points. Load it before crafting any LinkedIn messaging.
If no sales context file exists, ask:
- Who are you targeting? (Title, company size, industry)
- What do you sell? (One sentence — product/service + primary outcome)
- What's your LinkedIn presence like? (Follower count, posting frequency, profile completeness)
- What's the goal? (Book meetings, build relationships, generate referrals)
- Are you using Sales Navigator? (Changes targeting, InMail availability, and workflow design)
Core Principles
- Engage before you pitch. Comment on their posts, react to their content, share their articles — all before sending a connection request. They should recognize your name before you ask for anything.
- Connection request is not a pitch. The request is to connect. The pitch comes later (if ever). Combining them is the #1 mistake in LinkedIn outreach.
- Write like a human, not a sequence. LinkedIn messages that feel automated get ignored. If your message could be sent to 500 people unchanged, rewrite it.
- Your profile is your landing page. Before they reply, they visit your profile. If your headline says "Account Executive at Acme Corp," you've already lost. Make it about the value you bring to people like them.
- Patience beats volume. 20 thoughtful LinkedIn conversations beat 200 copy-paste InMails. This channel rewards relationship-building over spray-and-pray.
- Read the signals. LinkedIn gives you real-time buying signals — profile views, post engagement, connection accepts. Learn to read them and act on them.
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.
- 12d ago First seen · 455 lines · 124 tokens per session scan A 7c5d41892661
linkedin-outreach is a skill published in the GitHub repository TheCraigHewitt/sales-skills (24 stars, last pushed 5mo ago), licensed MIT. It adds 124 tokens to every session and 4,915 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to linkedin-outreach, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…