What is analytics-tracking?

A set of guidelines for deciding what user or marketing actions to measure with tools such as Google Analytics, Mixpanel, or Amplitude. It covers event tracking, conversion tracking, UTM campaign labels, and Google Tag Manager.

Use it to plan, set up, audit, name, document, and validate website or product analytics tracking.

It helps prevent collecting large amounts of inconsistent data that does not answer useful business questions.

analytics-tracking — Skill for Claude Code and Codex by Orkas-AI

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.

Any agent

npx skills add Orkas-AI/Orkas-Awesome-AgentSkills --skill analytics-tracking

Clone the repo

git clone --depth 1 https://github.com/Orkas-AI/Orkas-Awesome-AgentSkills

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/orkas-ai/orkas-awesome-agentskills/analytics-tracking/github.svg)](https://agentmods.dev/skills/orkas-ai/orkas-awesome-agentskills/analytics-tracking)

Your own site

<a href="https://agentmods.dev/skills/orkas-ai/orkas-awesome-agentskills/analytics-tracking"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas-awesome-agentskills/analytics-tracking/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/orkas-ai/orkas-awesome-agentskills/analytics-tracking"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas-awesome-agentskills/analytics-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,552 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00082	$0.02552
Opus 5	$0.00041	$0.01276
Sonnet 5	$0.00016	$0.00510
Haiku 4.5	$0.00008	$0.00255

Measured 12d ago against content hash d3619b093a80, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

analytics-tracking 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 12d 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.

Origin

This is a copy

100% identical to analytics-tracking — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

product/skills/marketing-skills/references/analytics-tracking/SKILL.md · 540 lines

How it starts

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

Analytics Tracking

You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.

Initial Assessment

Before implementing tracking, understand:

Business Context
- What decisions will this data inform?
- What are the key conversion actions?
- What questions need answering?
Current State
- What tracking exists?
- What tools are in use (GA4, Mixpanel, Amplitude, etc.)?
- What's working/not working?
Technical Context
- What's the tech stack?
- Who will implement and maintain?
- Any privacy/compliance requirements?

Core Principles

1. Track for Decisions, Not Data

Every event should inform a decision
Avoid vanity metrics
Quality > quantity of events

2. Start with the Questions

What do you need to know?
What actions will you take based on this data?
Work backwards to what you need to track

3. Name Things Consistently

Naming conventions matter
Establish patterns before implementing
Document everything

4. Maintain Data Quality

Validate implementation
Monitor for issues
Clean data > more data

Tracking Plan Framework

Structure

Event Name | Event Category | Properties | Trigger | Notes
---------- | ------------- | ---------- | ------- | -----

Event Types

Pageviews

Automatic in most tools
Enhanced with page metadata

User Actions

Button clicks
Form submissions
Feature usage
Content interactions

System Events

Signup completed
Purchase completed
Subscription changed
Errors occurred

Custom Conversions

Goal completions
Funnel stages
Business-specific milestones

Event Naming Conventions

Format Options

Object-Action (Recommended)

signup_completed
button_clicked
form_submitted
article_read

Action-Object

click_button
submit_form
complete_signup

Category_Object_Action

checkout_payment_completed
blog_article_viewed
onboarding_step_completed

Read the full file on GitHub · 540 lines

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.

12d ago First seen · 540 lines · 82 tokens per session scan A d3619b093a80

Subscribe to this mod's changes

analytics-tracking is a skill published in the GitHub repository Orkas-AI/Orkas-Awesome-AgentSkills (13 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 2,552 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to analytics-tracking, differing in 0 lines, and is treated as a copy.

Analytics and metrics Marketing and SEO agent-framework agent-skills ai-agents ai-tools automation awesome-list

viral-tech-reel-editor

End-to-end viral tech reel production for Instagram Reels and TikTok using 2026 trend grammar — retention-first pacing, punch-ins, 3D cinematic AI-generated shots, motion design graphics, proof b-roll, trending SFX, karaoke captions (Georgian/English), safe-zone layout, and QA-gated 1080x1920 export. This skill should…

tornikebolokadze1-cyber/awesome-ai-pulse-georgia · 172 tokens

implementing-aws-config-rules-for-compliance

Implementing AWS Config rules for continuous compliance monitoring of AWS resources, deploying managed and custom rules aligned to CIS and PCI DSS frameworks, configuring automatic remediation with SSM Automation, and aggregating compliance data across accounts.

adriannoes/awesome-agentic-ai · 53 tokens

analytics-tracking