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 Doris-Labs/sales-skills --skill cold-emailgit clone --depth 1 https://github.com/Doris-Labs/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/doris-labs/sales-skills/cold-email)<a href="https://agentmods.dev/skills/doris-labs/sales-skills/cold-email"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/cold-email/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/doris-labs/sales-skills/cold-email"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/cold-email.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.00065 | $0.01467 |
| Opus 5 | $0.00032 | $0.00733 |
| Sonnet 5 | $0.00013 | $0.00293 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
cold-email 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Email
Purpose
Write a first-touch email a busy stranger actually replies to: one problem, one relevance hook grounded in a real trigger, and one low-friction ask — not a pitch.
Inputs
- Who you're emailing (name, role, company)
- A real trigger or reason-to-reach-out-now (hire, funding, launch, post, mutual context)
- The one problem you solve for this persona
- A proof point you can cite (a similar customer, a result, a relevant pattern)
Method
- One problem per email. Pick the single pain that matters most to this persona and write only about that. A second idea halves the reply rate — save it for the follow-up.
- Open with a real relevance hook. The first line must prove you're writing to them, not a list — anchored to a trigger they'd recognise (a hire, a launch, a stage change, something they said publicly). No "Hope you're well" or "I came across your profile."
- Brevity. Under 90 words, 5 sentences or fewer. It must be readable on a phone lock screen without scrolling. Every sentence earns its place or gets cut.
- Single low-friction ask. Ask for interest or a reply, not a 30-minute meeting. "Worth a look?" / "Open to me sharing how?" beats "Do you have 30 mins Tuesday?" The ask is a yes/no, not a calendar negotiation.
- No feature-dumping. Name the outcome, not the toolset. One proof point, stated as a customer + result, beats a feature list. Lead with their world, not your product.
- Subject-line rules: 2–4 words, lowercase or sentence case, no caps, no emoji, no "Quick question," no "{Company} <> {YourCompany}." Make it look like an internal note from a colleague — reference their problem or trigger, never your product name.
Cold email skeleton:
Subject: <2–4 words, their problem/trigger>
Hi <name>,
<relevance hook tied to a real trigger — proves this isn't a blast>.
<the one problem this persona feels, in their language>.
<one proof point: similar customer + concrete result>.
<single low-friction yes/no ask>?
<first name>
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 · 150 lines · 65 tokens per session scan A 06a70c0fb571
cold-email is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 1,467 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
lynqu
Entry point for the Lynqu sales suite — describe any sales situation and it composes the right skills across capture, outreach, quoting and reporting. Requires the Lynqu MCP server connected.
lynqu-sales-playbook
Turn a written sales playbook into a live Lynqu pipeline — contacts, timed tasks, follow-up templates, the playbook attached to each lead, and stage rules that deliver the prep at the right moment.
lynqu-card-studio
Create and update Lynqu digital business cards — contact info, social links, services, template, palette — and check card views, scans and shares. Requires the Lynqu MCP server connected.
lynqu-competitors
Build a battlecard for the incumbent on a Lynqu deal — switching cost, wedge, objections and honest answers — written back to the lead. Requires the Lynqu MCP server.
lynqu-contacts
Map the buying committee on an account — economic buyer, champion, blocker — and write it into Lynqu as contacts and participants. Requires the Lynqu MCP server.
lynqu-deal-desk
Price a Lynqu deal and draft the quote — browse the price book, put priced lines on a deal, then produce a draft quote for a human to send. Requires the Lynqu MCP server connected.