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 tushaarmehtaa/tushar-skills --skill cold-outreachgit clone --depth 1 https://github.com/tushaarmehtaa/tushar-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/tushaarmehtaa/tushar-skills/cold-outreach)<a href="https://agentmods.dev/skills/tushaarmehtaa/tushar-skills/cold-outreach"><img src="https://agentmods.dev/badge/skills/tushaarmehtaa/tushar-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/tushaarmehtaa/tushar-skills/cold-outreach"><img src="https://agentmods.dev/badge/skills/tushaarmehtaa/tushar-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.00038 | $0.00751 |
| Opus 5 | $0.00019 | $0.00376 |
| Sonnet 5 | $0.00008 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold outreach
Write outreach that proves attention, makes one reasonable ask, and respects the recipient and applicable rules.
Choose a mode
- Single message: one email, introduction request, follow-up, or professional direct message.
- Sequence: coordinated touches with distinct purposes and stop conditions.
- Audit: diagnose existing copy, research, cadence, deliverability, or compliance risk.
- Reply handling: answer a positive reply, objection, referral, out-of-office, unsubscribe, or rejection.
Do not create a campaign when one message is enough.
Workflow
- Inspect supplied context and existing messages. Establish sender, recipient, relationship, goal, offer, proof, and requested next step without re-asking known facts.
- Research current recipient signals when research is authorized and useful. Prefer the person's work, company pages, filings/releases, job posts, interviews, and public writing. Record URLs and retrieval dates.
- Separate verified facts, sender-provided claims, and inference. Never invent familiarity, praise, mutual contacts, urgency, results, or social proof.
- Draft the shortest message that can establish relevance and make the ask. Use length and subject-line guidance as defaults, not universal laws.
- For a sequence, give every touch a different job and widening space where appropriate. Define stop conditions before copy.
- For reply handling, match the state: answer the question, reduce friction, propose the next step, or stop. Never continue after an opt-out.
- Check sender identity, authentication, list provenance, suppression handling, required identification/opt-out language, and applicable jurisdiction before recommending volume. If jurisdiction or recipient type is unknown, flag the legal uncertainty rather than declaring compliance.
- Read copy aloud. Remove generic flattery, throat-clearing, fake scarcity, hidden asks, manipulative guilt, and unsupported claims.
Ask only for a missing fact that materially changes the message. If a fact is useful but non-blocking, draft with a clearly marked confirmation note.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 60 lines · 38 tokens per session scan A fabc60de94f9
cold-outreach is a skill published in the GitHub repository tushaarmehtaa/tushar-skills (11 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 751 once invoked, about $0.0002 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
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…