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 san-npm/skills-ws --skill cold-outreachgit clone --depth 1 https://github.com/san-npm/skills-wsWrote 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/san-npm/skills-ws/cold-outreach)<a href="https://agentmods.dev/skills/san-npm/skills-ws/cold-outreach"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/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/san-npm/skills-ws/cold-outreach"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/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.00081 | $0.07190 |
| Opus 5 | $0.00041 | $0.03595 |
| Sonnet 5 | $0.00016 | $0.01438 |
| Haiku 4.5 | $0.00008 | $0.00719 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Outreach
Workflow
1. Deliverability Setup
Do this BEFORE sending a single email. Skipping this = spam folder.
DNS records (required) — publish only the ESP you actually send through. Do not copy a multi-include SPF "starter" record; each include: costs DNS lookups (SPF hard-fails at 10 lookups per RFC 7208) and an unused include both wastes a lookup and authorizes a sender you don't use.
# SPF — pick ONE example matching your ESP. Use ~all (softfail) while warming, -all once stable.
# Google Workspace: v=spf1 include:_spf.google.com ~all
# SendGrid: v=spf1 include:sendgrid.net ~all
# Microsoft 365: v=spf1 include:spf.protection.outlook.com ~all
# Amazon SES: v=spf1 include:amazonses.com ~all
# Most cold-email senders (Instantly/Smartlead) ship a dedicated domain — use the
# exact SPF/DKIM strings from THEIR setup wizard, not the strings above.
# DKIM — your ESP generates the keypair and gives you the exact TXT record + selector.
# Publish it verbatim. Prefer a 2048-bit key. Example selector:
sg._domainkey.example.com TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSq..." # value from ESP
# DMARC — start at p=none with reporting; tighten only after SPF+DKIM align cleanly for ~2 weeks.
_dmarc.example.com TXT "v=DMARC1; p=none; rua=mailto:[email protected]; fo=1"
Alignment, not strictness. DMARC passes on relaxed alignment by default (org-domain match), which is all Gmail/Yahoo require. Do not reflexively set
aspf=s; adkim=s— strict mode breaks legitimate setups where the ESP signs with a subdomain or rewrites the envelope (common with shared sending domains). Leave alignment relaxed (the default) unless you control every signing surface and have a specific spoofing reason.
Verify before you send (run these; don't trust the dashboard alone):
dig +short TXT example.com # SPF: exactly one v=spf1 record, <10 includes
dig +short TXT sg._domainkey.example.com # DKIM: your selector resolves to v=DKIM1 ...
dig +short TXT _dmarc.example.com # DMARC: v=DMARC1; p=...; rua=...
# Count SPF lookups (must stay <=10):
dig +short TXT example.com | grep -o 'include:' | wc -l
# End-to-end: send one message to a Gmail account, open "Show original" → expect
# SPF: PASS, DKIM: PASS, DMARC: PASS
If you use a click/open tracking domain, host it as a CNAME on a subdomain you control (e.g. track.example.com) and confirm it isn't on a blocklist — a shared/blacklisted tracking domain tanks deliverability even when auth passes.
What ships with it
1 file 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.
- 11d ago First seen · 387 lines · 81 tokens per session scan A a831acf28c45
cold-outreach is a skill published in the GitHub repository san-npm/skills-ws (2 stars, last pushed 4d ago), licensed MIT. It adds 81 tokens to every session and 7,190 once invoked, about $0.0004 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
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…