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 mfwarren/entrepreneur-claude-skills --skill cold-outreachgit clone --depth 1 https://github.com/mfwarren/entrepreneur-claude-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/mfwarren/entrepreneur-claude-skills/cold-outreach)<a href="https://agentmods.dev/skills/mfwarren/entrepreneur-claude-skills/cold-outreach"><img src="https://agentmods.dev/badge/skills/mfwarren/entrepreneur-claude-skills/cold-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/mfwarren/entrepreneur-claude-skills/cold-outreach"><img src="https://agentmods.dev/badge/skills/mfwarren/entrepreneur-claude-skills/cold-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.00003 | $0.01033 |
| Opus 5 | $0.00002 | $0.00517 |
| Sonnet 5 | $0.00001 | $0.00207 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
cold-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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Outreach
Cold email sequences, LinkedIn DMs, and personalized outreach that get replies. Structured around relevance, brevity, and clear value.
Purpose
Cold outreach fails when it's generic, long, or self-centered. This skill generates outreach that's short, specific to the recipient, and focused on their problem — not your product.
Workflow
Step 1: Gather Context
Collect from the user:
- What you sell: Product/service in one sentence
- Who you're targeting: Title, company size, industry
- Their likely pain: The problem they probably have right now
- Your proof: Results you've gotten for similar companies/people
- Channel: Email, LinkedIn DM, or both
- Sequence length: Single touch or multi-step (recommend 3-5 emails)
Step 2: Research the Recipient (if specific)
If targeting a specific person/company:
- Reference something specific (recent post, company news, job listing, product launch)
- Connect it to the pain your product solves
- Never fake personalization — if you can't find something real, use industry-level relevance
Step 3: Write the Sequence
Email 1: The Opener (Day 1)
- Subject line: Short, lowercase, curiosity or relevance-driven
- Line 1: Observation about them (not about you)
- Line 2-3: Connect to a problem they likely have
- Line 4: What you do and one proof point
- Line 5: Soft CTA (question, not demand)
- Total: 4-6 sentences max
Email 2: The Value Add (Day 3)
- Provide something useful — a quick insight, stat, or idea
- Don't pitch. Just demonstrate you understand their world.
- End with "Thought this might be relevant. Worth a quick chat?"
Email 3: The Case Study (Day 6)
- "We helped [similar company] achieve [specific result] in [timeframe]"
- One paragraph, one result, one CTA
- "Would something like this be useful for [their company]?"
Email 4: The Breakup (Day 10)
- Short and honest: "I'll stop reaching out, but wanted to leave this here"
- Restate the value one final time
- "If timing is ever right, here's my calendar: [link]"
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 · 134 lines · 3 tokens per session scan A 2b0d982e687b
cold-outreach is a skill published in the GitHub repository mfwarren/entrepreneur-claude-skills (67 stars, last pushed 7mo ago), licensed MIT. It adds 3 tokens to every session and 1,033 once invoked, about $0.0000 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-30.
Other skills, from other repositories
modelchk
Size a task's run before spending it: the cheapest sufficient capability tier (fast, standard, frontier) and the reasoning effort within it, on a neutral scale that binds to whatever levels the model exposes. Use when work seems over- or under-powered, costly, ambiguous, or high-risk, or asks which model class and how…
re0-loop
Run repeated build -> QA -> re0-memo -> re0-work cycles while preserving learning and letting code die. Use for long agentic projects where progress must be measured by quality-cleared templates, reusable modules, and eliminated anti-patterns rather than hours spent or features accumulated.
autobahn
Carve guardrail-adjacent items out of scope with safe alternatives before risk-adjacent work starts, then run the safe remainder at full strength in a fresh subagent that only ever sees the carved prompt, never the risky input. Use when a task includes stealth, scraping, privacy, IP, policy, licensing, security, or…
re0-release
Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.
ssotize
Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Use when asked to find duplication, check consistency, locate the source of truth, deduplicate, consolidate, unify, or establish SSOT across artifacts or platforms. Starts…
re0-plan
Open a paperthin iteration's casebook before re0-loop's first turn — seeded with real content the moment the folder exists, never an empty directory. User-invoked, paperthin-only: assumes the full skill package installed. Run when opening a new build cycle in this repo.