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 swan-gtm/gtm-skills --skill pre-conference-outreachgit clone --depth 1 https://github.com/swan-gtm/gtm-skillsWrote 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/swan-gtm/gtm-skills/pre-conference-outreach)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/pre-conference-outreach"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/pre-conference-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/swan-gtm/gtm-skills/pre-conference-outreach"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/pre-conference-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.00117 | $0.04184 |
| Opus 5.5 | $0.00047 | $0.01674 |
| Sonnet 5.5 | $0.00023 | $0.00837 |
| Haiku 4.5 | $0.00012 | $0.00418 |
Grade A, and why
pre-conference-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 25d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-conference outreach
Template placeholders
Replace every {{...}} before enabling. See the setup checklist reference for the full setup list.
{{EVENT_NAME}}- The conference as people say it in a DM (e.g. "GTM2026", "SaaStr"){{EVENT_CITY}}- Host city, used to pick "hitting the conf?" vs "Making the trip?"{{EVENT_DATES}}- Date range, used to pick "this week" vs "next week" at send time{{EXEC_SIDE_EVENT}}- Your executive side-door offer, as it reads in a sentence (e.g. "an exec dinner on Tuesday night"){{PRACTITIONER_SIDE_EVENT}}- Your hands-on side-door offer (e.g. "a skills hackathon during the conference", "a build session"){{EXEC_SENDER}}- Teammate with the authority lens: talks to whoever owns the problem and its budget{{SALES_LEADER_SENDER}}- Teammate with the seller-management lens: talks to people who manage sellers{{PRACTITIONER_SENDER}}- Teammate with the practitioner lens: talks to hands-on operators of the GTM stack{{EXEC_SENDER_MIN_ORG_SIZE}}- Employee count above which {{EXEC_SENDER}} may send (default: 100){{CRM}}- Your CRM (e.g. HubSpot, Attio, Salesforce){{SIGNAL_LIBRARY}}- Optional: your list of verified third-party angles and how to verify each (funding, hiring, product launches, stack changes){{ATTENDEE_TAG}}- The tag or memory line you use to record "this person attended {{EVENT_NAME}}"{{M1_CHAR_CAP}}- Hard character cap on the first email body (default: 250){{VOICE_GUIDE}}- Optional: a sender's voice guide to load when they are the sender
When to use this page
An attendee list for {{EVENT_NAME}} (or an explicit "run pre-conference outreach on these people") needs sequences that drive a meeting before or during the conference, plus a side-door CTA: {{EXEC_SIDE_EVENT}} for the exec and sales-leader senders, {{PRACTITIONER_SIDE_EVENT}} for the practitioner sender.
This is a reusable play. Swap the event fill-ins when the next conference is the instance. Sequence everyone on the file. Score or scoring tier does not route or skip anyone.
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.
- 25d ago First seen · 264 lines · 117 tokens per session scan A 04b8d7700b40
pre-conference-outreach is a skill published in the GitHub repository swan-gtm/gtm-skills (181 stars, last pushed 3d ago), licensed MIT. It adds 117 tokens to every session and 4,184 once invoked, about $0.0005 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-09-23.
Other skills, from other repositories
webhook-subscriptions
Webhook subscriptions: event-driven agent runs.
k8s-workload-inventory
List Kubernetes workloads and namespaces — pods with their node, phase and readiness, plus events. Use when asked what is running, where it is running, what is failing, or for a general inventory of a cluster.
luma-event-insights
Starter skill for analyzing Lu.ma events, attendees, invites, and engagement signals from organizer-provided API access, exports, or manual event inputs. Use this when a template or workflow needs a repeatable path to turn Lu.ma event data into an organizer-ready analysis brief.
huawei-cloud-cce-kubernetes-event-analyzer
Query and analyze Kubernetes Events in Huawei Cloud CCE clusters. Trigger when users ask about CCE events, Kubernetes warning events, FailedScheduling, FailedMount, ImagePullBackOff, event patterns, historical events in LTS, or event-based diagnosis for a CCE cluster or namespace.
cairo-contract-authoring
Cairo smart-contract authoring on Starknet. Trigger on "write a contract", "create a contract", "implement this in Cairo", "add storage/events/interface", "compose components". Guides structure, security patterns, and component wiring.
backend-event-sourcing
Use this skill when the user says 'event sourcing', 'event store', 'event stream', 'event sourced', 'rehydrate from events', 'event replay', 'projection rebuild', 'event log', 'append-only log', 'event history'. This skill enforces: events as the single source of truth, current state derived from event replay…