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 bcharleson/cursor-for-gtm-demo --skill cold-email-deliverabilitygit clone --depth 1 https://github.com/bcharleson/cursor-for-gtm-demoWrote 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/bcharleson/cursor-for-gtm-demo/cold-email-deliverability)<a href="https://agentmods.dev/skills/bcharleson/cursor-for-gtm-demo/cold-email-deliverability"><img src="https://agentmods.dev/badge/skills/bcharleson/cursor-for-gtm-demo/cold-email-deliverability/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/bcharleson/cursor-for-gtm-demo/cold-email-deliverability"><img src="https://agentmods.dev/badge/skills/bcharleson/cursor-for-gtm-demo/cold-email-deliverability.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.00072 | $0.01233 |
| Opus 5 | $0.00036 | $0.00616 |
| Sonnet 5 | $0.00014 | $0.00247 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade A, and why
cold-email-deliverability 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Email Deliverability
Deliverability is always top of mind. Legitimate cold outreach shares the same filtering environment as spam. Infrastructure and message format must earn inbox placement before copy or offers matter.
Agent Responsibilities
When deliverability is in scope:
- Audit before send — Check DNS auth, message format, and recipient-environment risks.
- Flag blockers immediately — Missing SPF, DKIM, or DMARC is a hard stop. Do not recommend sending until resolved.
- Default to safest format — Plain text, no links, no images, unless the user explicitly chooses otherwise.
Message Format Rules
Default (best practice)
- Plain text only — No HTML templates, no rich formatting.
- No links — URLs trigger marketing/spam heuristics. Omit unless intentionally doing so with eyes open on risk.
- No images — Same rationale as links.
- No attachments in initial cold touches — increases filter scrutiny.
When links or assets are intentional
If the user explicitly wants links (calendar, deck, video):
- Acknowledge deliverability tradeoff.
- Prefer sending the asset after a positive reply.
- Ensure domain reputation, DNS auth, and landing pages are solid (see SEG section).
Sending-Side Infrastructure
Every sending domain or inbox — Google Workspace, Microsoft 365, or custom SMTP — must have proper DNS authentication.
Required DNS records
| Record | Purpose | Agent action |
|---|---|---|
| SPF | Authorizes which servers may send for the domain | Verify present and includes only legitimate send sources |
| DKIM | Cryptographic signature proving message integrity | Verify signing is enabled and DNS publishes the public key |
| DMARC | Policy for failed SPF/DKIM; reporting | Verify policy exists (start with p=none for monitoring if needed, tighten over time) |
If any of SPF, DKIM, or DMARC is missing or misconfigured → flag immediately. Deliverability will suffer; do not proceed as if send-ready.
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 · 141 lines · 72 tokens per session scan A 45a232ac54cf
cold-email-deliverability is a skill published in the GitHub repository bcharleson/cursor-for-gtm-demo (2 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 1,233 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
objection-analyzer
Find out which objections your outbound gets, how well your team handled them, and what to say next time. Use whenever the user wants to analyze the objections in their replies, rank the most frequent ones, know how to handle a specific objection, coach reps on their objection answers, build an objection playbook or…
sales-nav-search-builder
Generate a precise LinkedIn Sales Navigator search URL from a natural-language ICP description — for sales prospecting, outbound outreach, lead generation, and B2B targeting. Use whenever the user asks for a Sales Nav URL, a LinkedIn search URL, an outbound prospecting query, a search for a persona or role, wants to…
reply-draft-assistant
Handle replies to your cold outreach end to end — classify each response, draft the right answer from the full conversation, and send it through La Growth Machine after you approve. Use any time the user has replies to handle: their LGM inbox ("who do I need to reply to?"), a campaign's replies, or a pasted thread.…
campaign-challenger
Challenge an outbound campaign copy by benchmarking it against the user's existing campaigns — what worked, what didn't, what the winners do differently — and return a concrete verdict plus prioritized fixes. Use whenever the user wants to know if a campaign or sequence is good, compare a draft to past campaigns…
multichannel-campaign-builder
Generate a complete multichannel outbound campaign — a full sequence of LinkedIn and email messages — from a natural-language brief. Use whenever the user wants to write an outreach campaign, create a prospecting sequence, draft a multichannel sequence, write cold emails and LinkedIn messages, build a social-selling…
cargo
Router for the Cargo CLI skill bundle — load first for anything Cargo, and whenever a task spans two Cargo domains. Explains what each skill owns, declarative workspace-as-code (cargo-cdk) vs the imperative CLI, the UUID and slug flow between skills, async polling of runs and batches, end-to-end use cases, and the…