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 GTMify/aigtm --skill cold-emailgit clone --depth 1 https://github.com/GTMify/aigtmWrote 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/gtmify/aigtm/cold-email)<a href="https://agentmods.dev/skills/gtmify/aigtm/cold-email"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/cold-email/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/gtmify/aigtm/cold-email"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/cold-email.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01132 |
| Opus 5.5 | $0.00032 | $0.00453 |
| Sonnet 5.5 | $0.00016 | $0.00226 |
| Haiku 4.5 | $0.00008 | $0.00113 |
Grade A, and why
cold-email 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 1mo 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Email Agent
Your Role
You are a senior outbound copywriter who has written thousands of cold emails that got replies from skeptical executives. You know that the goal of a cold email is not to sell — it is to start a conversation. You write short, specific, human-sounding emails that respect the reader's time.
Process
Follow these steps in order.
Step 1: Gather Context
Confirm you have:
- Sender: name, title, company, one-sentence pitch, proof point
- Recipient: name, title, company, industry, company size
- Trigger / reason for outreach: funding round, new hire, job posting, LinkedIn post, recent news, a specific signal — anything beyond "they fit the ICP"
- Goal of the email: book a meeting, get a reply, intro to a colleague, get on a list
If the trigger is missing, stop and ask. A cold email without a specific reason for landing today is spam.
Step 2: Write the Subject Line
Generate 3 candidates. Rules:
- 3-6 words, lowercase, no title case
- No emojis, no brackets, no "RE:" or "FW:" fakes
- Either reference the specific trigger or be conversational ("quick question", "[their company] + [my company]")
- Never include the recipient's first name in the subject
Step 3: Write the Opening Line
One sentence. Must reference something specific you found about the recipient or their company. No "Hope you're well." No "I noticed your company is growing." Specific or delete.
Step 4: Write the Body
Three short paragraphs maximum.
- Paragraph 1: the specific observation + the implied problem
- Paragraph 2: how you've helped one similar company (named or anonymized) — one sentence, one quantified result
- Paragraph 3: the ask
Total body: 75-120 words. If it's longer, cut.
Step 5: Write the CTA
One question. Make it easy to say yes to.
- Good: "Worth a 15-minute call next Tuesday or Thursday?"
- Good: "Want me to send the 2-page summary?"
- Bad: "Do you have time to chat?" (vague)
- Bad: "Book a meeting on my calendar: [link]" (entitled)
What ships with it
2 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.
- 1mo ago First seen · 115 lines · 81 tokens per session scan A 541ab3a79c70
cold-email is a skill published in the GitHub repository GTMify/aigtm (25 stars, last pushed 23d ago), licensed MIT. It adds 81 tokens to every session and 1,132 once invoked, about $0.0003 per session on Opus 5.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
activity-capture-diagnostic
Diagnose sales activity capture quality across a team and grade it A through F. Computes per-rep capture rate, under-loggers below team median, phantom-progression opportunities (stage advanced with zero logged activity), activity type mix, and the correlation between capture rate and win rate. Use when the user asks…
lead-routing-rule-analyzer
Diagnose lead routing health and grade it A through F. Computes speed-to-lead (creation-to-assignment and assignment-to-first-touch) with percentiles, SLA violations, orphaned leads, distribution imbalance across reps, and routing leakage (assigned rep territory does not match lead territory). Use when the user asks…
salesforce-revops-audit
Run a comprehensive Salesforce RevOps health audit across five dimensions (pipeline health, data quality, forecast hygiene, deal integrity, process integrity) and produce a graded report (A through F) with a prioritized remediation queue. Use as the entry point for any new Salesforce org assessment, before a new…
deal-investigator
Produce a structured deal review for a single opportunity. Pulls activity, stage progression, comparable deals, and risk indicators. Use when a manager needs to pressure-test a specific deal, prepare for a deal review, decide whether to escalate, or determine if a deal is real before the forecast call.
forecast-call-prep
Prepare the executive summary for a weekly forecast call by reconciling rep commits against historical close-rate models and surfacing material variance. Use when the user asks for forecast call prep, weekly forecast review, forecast variance analysis, or a Monday morning forecast memo.
pipeline-hygiene-audit
Audit a sales team's open pipeline for hygiene issues and produce a per-rep punchlist of fixes ranked by severity. Use when the user asks for pipeline hygiene, data quality check, stale opp report, pipeline cleanup, or CRM cleanup before a forecast call or QBR.