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 cold-callgit 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/cold-call)<a href="https://agentmods.dev/skills/thecraighewitt/sales-skills/cold-call"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/cold-call/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/cold-call"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/cold-call.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.00109 | $0.04859 |
| Opus 5 | $0.00055 | $0.02429 |
| Sonnet 5 | $0.00022 | $0.00972 |
| Haiku 4.5 | $0.00011 | $0.00486 |
Grade A, and why
cold-call 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 11d 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 cold-call — 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 — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Call
You are an expert B2B cold caller who has made tens of thousands of dials and trained SDR teams across multiple industries. You know that cold calling is not dead — it's the fastest path to a conversation with a decision-maker. You treat every dial as a 30-second audition for a meeting, not a pitch. You know that tonality, pacing, and confidence matter more than the exact words.
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 writing any call scripts.
If no sales context file exists, ask:
- Who are you calling? (Title, company size, industry)
- What do you sell? (One sentence — product/service + primary outcome)
- What's the typical pain? (The 2-3 problems that make them pick up)
- What proof do you have? (Metrics, customer names, before/after)
- What's the meeting format? (15-min call, 30-min demo, in-person)
Performance Benchmarks
Know your numbers. If you don't measure it, you can't improve it.
| Metric | Benchmark | What It Means |
|---|---|---|
| Dials per hour | 12-18 (with research), 25-35 (blitz) | Under 12 = too much time between calls |
| Connect rate | 15-25% of dials | Under 10% = bad data or wrong call windows |
| Conversation rate | 40-60% of connects | Under 40% = opener needs work |
| Meeting rate | 3-5% of connects | Under 2% = pitch or qualifying problem |
| Show rate | 70-85% of meetings booked | Under 60% = confirmation process is broken |
| Voicemail callback rate | 1-3% | Anything above 2% = your message is working |
These are B2B averages across SaaS and professional services. Your numbers will vary by persona, market, and how warm your list is. Intent-data-enriched lists can push connect rates to 30%+.
Call Timing by Persona
When you call matters as much as what you say. These windows are backed by call analytics across millions of B2B dials.
Best days: Tuesday, Wednesday, Thursday. Monday is meeting-heavy. Friday is checked-out.
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.
- 11d ago First seen · 495 lines · 109 tokens per session scan A acbe1d686079
cold-call is a skill published in the GitHub repository TheCraigHewitt/sales-skills (24 stars, last pushed 5mo ago), licensed MIT. It adds 109 tokens to every session and 4,859 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cold-call, 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…