Claude Code Templates is a command-line tool and catalogue for configuring Anthropic’s Claude Code with agents, commands, settings, hooks, integrations, skills, and project templates. Developers use it to browse and install reusable components for their coding workflows. The catalogue includes many of these Claude Code components.
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 agentmods add skills/davila7/claude-code-templates/analytics-trackingnpx skills add davila7/claude-code-templates --skill analytics-trackinggit clone --depth 1 https://github.com/davila7/claude-code-templatesWrote 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/davila7/claude-code-templates/analytics-tracking)<a href="https://agentmods.dev/skills/davila7/claude-code-templates/analytics-tracking"><img src="https://agentmods.dev/badge/skills/davila7/claude-code-templates/analytics-tracking.svg" alt="Measured on agentmods" 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 | $0.00082 | $0.02552 |
| Opus 5 | $0.00041 | $0.01276 |
| Sonnet 5 | $0.00016 | $0.00510 |
| Haiku 4.5 | $0.00008 | $0.00255 |
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 yesterday.
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.
Copies of this mod
3 near-identical copies found in the catalogue:
- analytics-tracking — 100% identical, 0 lines differ
- analytics-tracking — 100% identical, 0 lines differ
- analytics-tracking — 98% identical, 3 lines differ
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
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.
- yesterday First seen · 540 lines · 82 tokens per session scan A d3619b093a80
analytics-tracking is a skill published in the GitHub repository davila7/claude-code-templates (30,533 stars, last pushed today), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
chief-data-officer-advisor
../../../c-level-advisor/skills/chief-data-officer-advisor/SKILL.md.
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
ai-act-readiness
../../../compliance-os/skills/ai-act-readiness/SKILL.md.
ai-security
../../../engineering-team/skills/ai-security/SKILL.md.
api-design-reviewer
../../../engineering/skills/api-design-reviewer/SKILL.md.