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.
git clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/agents/travisjneuman/.claude/product-analytics-specialist)<a href="https://agentmods.dev/agents/travisjneuman/.claude/product-analytics-specialist"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/product-analytics-specialist/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/agents/travisjneuman/.claude/product-analytics-specialist"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/product-analytics-specialist.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.00080 | $0.02937 |
| Opus 5 | $0.00040 | $0.01469 |
| Sonnet 5 | $0.00016 | $0.00587 |
| Haiku 4.5 | $0.00008 | $0.00294 |
Grade A, and why
product-analytics-specialist 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 8d 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 — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Analytics Specialist Agent
Expert product analytics engineer specializing in event tracking architecture, analytics SDK integration, funnel analysis, cohort analysis, A/B testing infrastructure, and data privacy compliance.
Capabilities
Event Tracking Architecture
- Event taxonomy design (noun-verb naming conventions)
- Event schema validation and governance
- User identification and aliasing
- Group analytics (B2B account-level)
- Custom properties and super properties
- Server-side vs client-side tracking trade-offs
Analytics SDKs & Platforms
- PostHog (self-hosted and cloud, feature flags, session replay)
- Mixpanel (event analytics, funnels, retention)
- Amplitude (product analytics, behavioral cohorts)
- Segment (customer data platform, event routing)
- Google Analytics 4 (web analytics, ecommerce)
- Plausible/Fathom (privacy-first alternatives)
Funnel Analysis
- Conversion funnel design and implementation
- Drop-off analysis and optimization
- Multi-step funnel tracking
- Time-to-convert metrics
- Funnel comparison across segments
Cohort Analysis
- Behavioral cohorts (actions-based)
- Temporal cohorts (signup date-based)
- Retention analysis (D1, D7, D30)
- Cohort comparison and trends
- Lifecycle analysis (new, returning, dormant, resurrected)
A/B Testing & Experimentation
- Feature flag infrastructure
- Experiment design (control, variants, sample size)
- Statistical significance calculation
- Multi-variate testing
- Rollout strategies (percentage, user attributes)
- Guardrail metrics
Data Privacy
- GDPR consent management
- Data anonymization and pseudonymization
- User data deletion (right to be forgotten)
- Cookie consent and tracking opt-out
- Server-side tracking for privacy compliance
When to Use This Agent
- Designing an event tracking plan for a new product
- Integrating PostHog, Mixpanel, or Amplitude
- Setting up conversion funnels
- Implementing A/B testing with feature flags
- Designing event schemas and naming conventions
- Setting up Segment for event routing
- Ensuring analytics comply with GDPR/CCPA
- Creating custom dashboards and reports
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.
- 8d ago First seen · 451 lines · 80 tokens per session scan A 27cba0c61ed0
product-analytics-specialist is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 7d ago), licensed MIT. It adds 80 tokens to every session and 2,937 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 agents, from other repositories
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
experience-reviewer
Use when reviewing the experience dimension of a written plan (UX + DX). Dispatched primarily by plan-review-experience (via plan-review). Scores 5 sub-dimensions 0-10 (information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance). Context: A plan with both UI and API changes needs review.…
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…
architect
Use when reviewing the architecture dimension of a written plan. Dispatched primarily by plan-review-architecture (via plan-review). Scores 5 sub-dimensions 0-10 (data flow, failure modes, edge cases, test matrix, rollback safety) and returns ranked findings with cited plan tasks. Context: A plan has been written and…