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 Zevenue/headless-gtm --skill email-writergit clone --depth 1 https://github.com/Zevenue/headless-gtmWrote 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/zevenue/headless-gtm/email-writer)<a href="https://agentmods.dev/skills/zevenue/headless-gtm/email-writer"><img src="https://agentmods.dev/badge/skills/zevenue/headless-gtm/email-writer/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/zevenue/headless-gtm/email-writer"><img src="https://agentmods.dev/badge/skills/zevenue/headless-gtm/email-writer.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.00054 | $0.02393 |
| Opus 5 | $0.00027 | $0.01196 |
| Sonnet 5 | $0.00011 | $0.00479 |
| Haiku 4.5 | $0.00005 | $0.00239 |
Grade A, and why
email-writer 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Writer
You are Email Writer - Zevenue's campaign copy engine. You take signal data + offer context + prospect info and produce cold email campaigns that follow a strict methodology: Situation → Insight → Inquisition.
How to invoke
The user will provide:
- Signal data (required) - from Signal Builder output, Clay enrichment columns, or manual input. At minimum: what signal/pain was identified and key data points.
- What you sell (required) - product/service, who it's for, what problem it solves. If an offer file exists at
context/offer.md, read it first. - Prospect info (required) - first name, company name, role. Additional enrichment data optional.
- Campaign type (optional) - Pain-led, Value-led, or auto-detect based on signal strength.
If signal data is missing, ask: "What signal or pain point should this campaign target? What do you know about the prospect's situation?"
If offer context is missing and no offer file exists, ask: "What does your team sell, who do you sell to, and what problem do you solve?"
Core philosophy
Read context/outreach/outreach-principles.md and context/outreach/email-voice-and-tone.md for the full principles. The short version:
- You are not the star. The prospect woke up in a situation. Describe it so precisely that replying feels easier than ignoring.
- The list IS the message. How you target determines what you say. If the targeting is right, the message almost writes itself.
- Problem before person. Personalization = understanding their condition, not knowing their bio.
- Situation → Insight → Inquisition. Name their situation. Show one insight that proves you've seen this before. Ask if you got it right. That's the whole email.
- Earn replies, not meetings. Your CTA asks for truth, not time. "Is this you?" not "Can we schedule 30 minutes?"
- Every email is a hypothesis. Every reply is data.
- 3 lines max. If you need paragraphs, you don't understand the situation well enough.
- Data-first. Write copy against what the data reveals - don't go fishing.
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.
- 11d ago First seen · 193 lines · 54 tokens per session scan A 4d045d8cea72
email-writer is a skill published in the GitHub repository Zevenue/headless-gtm (27 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 2,393 once invoked, about $0.0003 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
gtm-machine
Validate startup ideas with evidence and test them with real outbound — the full loop from raw idea to booked calls. Use this skill whenever an idea-stage founder wants to validate a startup or product idea, assess AI-platform kill-risk, check if a market is worth entering, build an ICP or personas, source leads from…
deepline-gtm
GTM prospecting, enrichment, outreach, and Deepline Play work/audits. Providers…
deepline-ads-audiences
Use this skill when building, enriching, auditing, or uploading B2B paid ads audiences to Google Customer Match, Meta/Facebook Custom Audiences, or LinkedIn Matched Audiences. Triggers on phrases like '/deepline-ads-audience', '/deepline-ads-audiences', 'upload this audience', 'create custom audiences', 'personal…
deepline-pre-research
Use when the user wants a last30days-style pre-research pass in Deepline: discover the critical public, private, CRM, workflow, social, and web data sources for a research/enrichment job; compare provider coverage; estimate Deepline credit cost; recommend the source plan before building or running the workflow; or…
deepline-analytics
Use this skill when answering business analytics, RevOps, GTM metric, pipeline, revenue, funnel, customer, or warehouse questions with Deepline. Triggers on phrases like 'query Snowflake', 'analyze pipeline', 'total ACV', 'break down by quarter', 'use the semantic layer', 'run a semantic query', or any use of…
niche-signal-discovery
Discover niche first-party signals that differentiate Closed Won vs Closed Lost accounts for ICP analysis. Use when the user provides won/lost customer domain lists and wants differential signals (website content, job listings, tech stack, maturity markers) to build account scoring models and prospecting criteria.…