event-analytics

event-analytics is a skill for Claude Code, Codex from LeadMagic/gtm-skills. It costs 107 tokens per session (2,922 once invoked), scanned A, original, MIT.

A framework for tracking customer actions, such as signups, clicks, feature use, upgrades, and cancellations, across sales, support, marketing, and product systems. It includes event naming, implementation, automated responses, and combined customer views.

In plain words
What is it for?
Use it to design an event catalogue, add tracking with tools such as Segment or Amplitude, connect customer events, and build event-based reports or workflows.
Why use it?
It prevents inconsistent tracking that produces confusing data instead of useful customer history.

Skill for Claude CodeCodex

Part of the gtm-skills plugin — 196 skills shipped together

Install

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.

agentmods
npx agentmods add skills/leadmagic/gtm-skills/event-analytics
Any agent
npx skills add LeadMagic/gtm-skills --skill event-analytics
Clone the repo
git clone --depth 1 https://github.com/LeadMagic/gtm-skills

Made for: Claude Code, Codex.

Or install gtm-skills, the plugin that ships this one along with the rest of its 196 skills.

Wrote 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.

agentmods badge for event-analytics

README.md
[![agentmods](https://agentmods.dev/badge/skills/leadmagic/gtm-skills/event-analytics.svg)](https://agentmods.dev/skills/leadmagic/gtm-skills/event-analytics)
Your own site
<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/event-analytics"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/event-analytics.svg" alt="Measured on agentmods" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,922 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00107 $0.02922
Opus 5 $0.00053 $0.01461
Sonnet 5 $0.00021 $0.00584
Haiku 4.5 $0.00011 $0.00292

Measured today against content hash 28de2ce0483b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

event-analytics 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 today.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/check-output.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/analytics/event-analytics/SKILL.md · 316 lines

How it starts

The opening of the file, as written. The whole thing — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Event Analytics

Overview

Events are the atomic unit of customer understanding. Every signup, click, feature use, upgrade, and cancellation is an event. The mistake: tracking events haphazardly ("track everything!") with no taxonomy, creating a data swamp instead of a data pipeline. This skill covers event analytics across every GTM system — how to design an event taxonomy, implement tracking, and unify event data across your stack to build a complete customer picture.

Authoritative Foundations

  • Segment — Customer Data Platform (CDP) and event taxonomy — Customer Data Platform (CDP) and event taxonomy
  • Amplitude — Behavioral analytics and event design — Behavioral analytics and event design
  • Mixpanel — Product analytics and event-based reporting — Product analytics and event-based reporting
  • Intercom — Event-driven messaging and automation — Event-driven messaging and automation
  • Avo — Event taxonomy and governance — Event taxonomy and governance
  • Snowplow — Open-source event pipeline — Open-source event pipeline

When to Use

Trigger phrases: "event analytics setup", "customer event tracking", "implement Segment", "Amplitude setup for SaaS", "event taxonomy design", "customer data pipeline", "product analytics events", "Intercom events", "event-driven workflows"

Step-by-Step Process

Phase 1: Event Taxonomy Design

The 4 event types (Segment spec):

  1. Identify: Who is the user? identify(userId, traits)
  2. Track: What did they do? track(eventName, properties)
  3. Page: What page did they view? page(name, properties)
  4. Group: What account/workspace are they in? group(groupId, traits)

Event naming convention (object-action framework):

Format: [Object] [Action] (Past tense. Write events as things that HAPPENED.)

Good: "Project Created" "Invoice Paid" "Campaign Sent"
Bad: "createProject" "user_clicked_button" "page3-conversion-v2"

Rules:
- Title case: "Signed Up" not "signed_up"
- Past tense: "Viewed" not "View"
- Object first: "Report Exported" not "Exported Report"
- No technical jargon: "Payment Completed" not "stripe_webhook_200"

Read the full file on GitHub · 316 lines

Files

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.

Changes

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.

  1. today Changed 28de2ce0483b
  2. 4d ago First seen · 316 lines · 107 tokens per session scan A 3ef7f39de2a6

Subscribe to this mod's changes

event-analytics is a skill published in the GitHub repository LeadMagic/gtm-skills (46 stars, last pushed 2d ago), licensed MIT. It adds 107 tokens to every session and 2,922 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

outreachmagic

Your agent goes blind after send. Sync sequencer webhooks, research leads via Serper, and find/verify emails — all in one local SQLite DB your agent queries directly.

outreachmagic/outreachmagic · 40 tokens

cold-email

Expert cold email strategist for B2B outbound campaigns. Use when the user asks about cold email writing, email sequences, email deliverability, domain warmup, SPF/DKIM/DMARC setup, email personalization, cold email templates, email copywriting frameworks, email compliance (CAN-SPAM, GDPR), bounce management, inbox…

Frontal-so/outbound-skills · 177 tokens

list-building

Expert B2B list building orchestrator for outbound sales campaigns. Use when the user asks about building lead lists, Sales Navigator search, boolean filters, ICP definition, ICP scoring, lead sources, data validation, email verification, list segmentation, Apollo prospecting, Clay Find People, list hygiene…

Frontal-so/outbound-skills · 190 tokens

claygent

Use Clay's AI research agent (Claygent) for web research, custom data extraction, and information that does not exist in standard databases. Use when the user asks about Claygent, AI research in Clay, web browsing for data, custom data points, real-time company research, or scraping with AI. Triggers on "Claygent"…

Frontal-so/outbound-skills · 131 tokens

conditional-logic

Write Clayscript formulas, conditional runs, and credit-saving logic in Clay. Use when the user asks about Clayscript, Clay formulas, conditional runs, saving credits with logic, data manipulation, if/then logic, JavaScript formulas in Clay, or the AI formula generator. Triggers on "Clayscript", "formula"…

Frontal-so/outbound-skills · 128 tokens

people-enrichment

Find and enrich contacts at target companies in Clay. Use when the user asks about finding decision makers, people enrichment, LinkedIn enrichment, title or seniority filtering, buying committee mapping, contact discovery at companies, or Sales Navigator imports. Triggers on "find contacts", "find people", "people…

Frontal-so/outbound-skills · 110 tokens