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 event-lead-ingestiongit 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/event-lead-ingestion)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/event-lead-ingestion"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/event-lead-ingestion/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/event-lead-ingestion"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/event-lead-ingestion.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.00171 | $0.03086 |
| Opus 5.5 | $0.00068 | $0.01234 |
| Sonnet 5.5 | $0.00034 | $0.00617 |
| Haiku 4.5 | $0.00017 | $0.00309 |
Grade A, and why
event-lead-ingestion 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 6d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Applies when someone on the team pastes a LinkedIn URL or work email from an in-person event conversation and wants the lead captured consistently: CRM, account memory, event tag, then the right next step.
This is not a list-upload play. It handles one named person (or a short named list in one message) from a real conversation. Badge-scan CSVs, dinner or registration lists, and web form submissions belong to your list-based post-event processes.
Preferred input is a LinkedIn URL. A work email is enough. A name plus company is the last resort.
Template placeholders
Replace every {{...}} before enabling. See the setup checklist reference for the full list and the decisions behind each.
{{CRM}}: Your CRM (e.g. HubSpot, Salesforce, Attio){{CRM_UPDATE_RULES}}: Your rules for creating and updating companies and contacts in{{CRM}}(dedupe, required fields, which fields never get overwritten){{ACCOUNT_MEMORY}}: Where durable account notes live (e.g. your agent's account memory, a CRM notes field, a shared doc per account){{COMPETITOR_LIST}}: Your competitor watchlist (domains and company names){{SCORING_PROCESS}}: Your account scoring process: tiers, persona gates, the employee and funding gate that marks self-serve accounts, and any alerts or MQL posts it owns{{TIER_NAMES}}: Your top account tiers (default: Gold and Diamond){{CONTACT_MAPPING_PROCESS}}: Optional: how you find more people in the buying committee at an account{{CLOSED_LOST_REACTIVATION}}: Optional: your process for re-engaging closed-lost accounts{{STAGE_SYNC}}: How account stage moves get pushed from your agent or scoring system into{{CRM}}, if they are separate{{EVENT_CALENDAR}}: Where each event you attend has a page with its name, dates and attendee tag (e.g. a shared doc, a Notion database){{EVENT_TAG_FORMAT}}: Your event attendee tag convention (default:evt:[slug]-[mmm-yy]){{OUTREACH_PLAYBOOK}}: Your outreach rules: routing paths, pre-flight gates, pitch by persona, writing style{{SEQUENCE_TOOL}}: Where sequences are built and staged (e.g. Outreach, Salesloft, Apollo, your agent's sequence builder){{LINKS_AND_RESOURCES}}: Where current demo and booking URLs live{{TASK_TOOL}}: Where personal tasks are created (e.g. your CRM tasks, Asana, your agent's task desk){{REMINDER_TOOL}}: How a one-time scheduled reminder is created (e.g. a scheduled agent run, a CRM task with a due date){{PRIVATE_NOTIFY}}: How the requester is pinged privately (e.g. a Slack DM)
What ships with it
3 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.
- 6d ago First seen · 184 lines · 171 tokens per session scan A 4552d005d7d9
event-lead-ingestion is a skill published in the GitHub repository swan-gtm/gtm-skills (219 stars, last pushed 5d ago), licensed MIT. It adds 171 tokens to every session and 3,086 once invoked, about $0.0007 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-10-19.
Other skills, from other repositories
a-b-testing
Design statistically sound GTM experiments for copy, channels, landing pages, sequencing, pricing, and funnel conversion. Produces hypothesis, sample-size logic, success metrics, test plan, analysis method, and scale/stop/kill recommendation. Use when planning A/B tests, split tests, or experiment roadmaps.
attribution
Build practical B2B attribution models across first touch, lead creation, opportunity creation, multi-touch, account-based influence, and sales-sourced revenue. Produces model comparison, UTM governance, source-of-truth rules, and channel ROI view. Use when marketing and sales disagree on source or ROI.
campaign-analytics
Analyze campaign performance from deliverability through revenue: delivery, engagement, replies, meetings, SQOs, pipeline, CAC, and payback. Produces diagnostic scorecard, root-cause analysis, benchmark comparison, and next-action plan. Use when deciding whether to scale, fix, or kill campaigns.
deliverability-monitoring
Monitor outbound deliverability health across domains, inboxes, DNS, bounces, spam placement, reply rates, and reputation signals. Produces alert thresholds, dashboard spec, weekly QA checklist, and remediation playbook. Use when inboxing drops, bounce rates rise, campaigns underperform, or new infrastructure launches.
gtm-metrics
Build a GTM metrics system for SaaS: funnel conversion, pipeline velocity, win rates, CAC, payback, NRR, sales efficiency, growth accounting, and executive dashboards. Use when creating metrics dashboards, board reports, revenue reviews, operating cadence, or diagnosing growth constraints.
tracking-plan
Master analytics tracking plan for PLG and B2B SaaS — unified event taxonomy, pixel strategy (1P and 3P tagging), marketing attribution architecture, CDP implementation (Segment, Rudderstack), product analytics (Amplitude, Mixpanel, PostHog), CRM tracking (HubSpot, Salesforce), and analytics infrastructure design. Use…