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 gtm-outreachgit 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/gtm-outreach)<a href="https://agentmods.dev/skills/bcharleson/cursor-for-gtm-demo/gtm-outreach"><img src="https://agentmods.dev/badge/skills/bcharleson/cursor-for-gtm-demo/gtm-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/bcharleson/cursor-for-gtm-demo/gtm-outreach"><img src="https://agentmods.dev/badge/skills/bcharleson/cursor-for-gtm-demo/gtm-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.00063 | $0.00622 |
| Opus 5.5 | $0.00025 | $0.00249 |
| Sonnet 5.5 | $0.00013 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
gtm-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 2mo 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTM Outreach
When to Use This Skill
Apply this skill as the entry point for any cold outreach work in this project. Route to specialized skills based on the task.
Skill Routing
| User need | Read and follow |
|---|---|
| Inbox placement, DNS auth, ESP/SEG setup, sending infrastructure | cold-email-deliverability |
| Writing, editing, or reviewing email copy | cold-email-copywriting |
| LinkedIn messaging or connection requests | Coming soon — apply email copy principles until dedicated skill exists |
Outreach Stack (Mental Model)
Sending infrastructure Message Recipient environment
───────────────────── ─────── ─────────────────────
SPF / DKIM / DMARC → Plain text, relevant → Google / Microsoft / custom ESP
Domain reputation Hook → Bridge → CTA SEGs (Proofpoint, Mimecast…)
Plain text, no links Low-friction ask Corporate security filters
Agent Workflow
- Clarify the goal — Who is the ICP? What is the offer? What outcome does the user want (reply, meeting, asset sent)?
- Check infrastructure first — Before drafting or approving send plans, verify deliverability prerequisites via the deliverability skill.
- Draft or review copy — Use the copywriting skill. Never approve copy that violates deliverability rules unless the user explicitly opts in.
- Validate as a unit — Infrastructure + copy + CTA must align. A great email on a broken domain still fails.
Non-Negotiables
- Deliverability is always top of mind.
- Cold email defaults to plain text with no links or images unless the user intentionally chooses otherwise.
- Missing SPF, DKIM, or DMARC must be flagged immediately — do not treat as optional.
- No small talk, no flattery openers, no novels.
- CTAs should be low-friction; hard asks for meetings are the exception, not the rule.
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.
- 2mo ago First seen · 62 lines · 63 tokens per session scan A df063399f865
gtm-outreach is a skill published in the GitHub repository bcharleson/cursor-for-gtm-demo (2 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 622 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-31.
gtm-outreach compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| gtm-outreachbcharleson/cursor-for-gtm-demo | Skill | 2 | 4mo ago | MIT | A | 63 | Cursor |
| cargo-orchestrationgetcargohq/cargo-skills | Skill | 21 | yesterday | MIT | A | 205 | Claude Code |
| cargo-aigetcargohq/cargo-skills | Skill | 21 | yesterday | MIT | A | 167 | Claude Code |
| cargo-hostinggetcargohq/cargo-skills | Skill | 21 | yesterday | MIT | A | 180 | Claude Code |
| cargo-contextgetcargohq/cargo-skills | Skill | 21 | yesterday | MIT | A | 162 | Claude Code |
| cargo-storagegetcargohq/cargo-skills | Skill | 21 | yesterday | MIT | A | 168 | Claude Code |
| cargo-workspace-managementgetcargohq/cargo-skills | Skill | 21 | yesterday | MIT | A | 151 | Claude Code |