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/0xranx/agentbrief/analytics-setupnpx skills add 0xranx/agentbrief --skill analytics-setupgit clone --depth 1 https://github.com/0xranx/agentbriefWhat 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.00074 | $0.00888 |
| Opus 5 | $0.00037 | $0.00444 |
| Sonnet 5 | $0.00015 | $0.00178 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
analytics-setup 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 2d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics Setup
You are setting up product analytics that answer real business questions. Your goal is to create a tracking plan that captures meaningful user behavior without drowning in noise.
Process
1. Define Key Questions
Before adding any tracking code, list the top 5 questions you need to answer:
- Are users activating? (Reaching the "aha moment")
- Are users coming back? (Retention)
- Where do users drop off? (Funnel leaks)
- Which features drive engagement? (Feature adoption)
- What brings users to the product? (Attribution)
2. Design the Event Taxonomy
Use a consistent naming convention:
[object]_[action]
Examples:
- page_viewed
- signup_started
- signup_completed
- feature_used
- subscription_started
- subscription_cancelled
- error_occurred
Rules:
- Past tense for completed actions (
signup_completednotsignup) - Snake_case, lowercase
- Object first, then action
- Include properties for context, not in the event name
3. Core Events (Every Product Needs These)
// Identification
analytics.identify(userId, {
email: user.email,
created_at: user.createdAt,
plan: user.plan,
});
// Page / Screen Views
analytics.page('Dashboard');
// Activation Funnel
analytics.track('signup_started', { source: 'landing_page' });
analytics.track('signup_completed', { method: 'google_oauth' });
analytics.track('onboarding_step_completed', { step: 1, step_name: 'create_workspace' });
analytics.track('activation_completed'); // User hit the "aha moment"
// Feature Usage
analytics.track('feature_used', {
feature_name: 'export_csv',
context: 'dashboard',
});
// Revenue
analytics.track('subscription_started', {
plan: 'pro',
billing_cycle: 'annual',
mrr: 29,
});
4. Platform Selection Guide
| Tool | Best For | Price |
|---|---|---|
| PostHog | Self-hosted, open source, full suite | Free (self-hosted) |
| Mixpanel | Event analytics, funnels, retention | Free up to 20M events |
| Amplitude | Product analytics at scale | Free up to 10M events |
| GA4 | Marketing analytics, attribution | Free |
| Plausible | Privacy-friendly, simple web analytics | $9/mo |
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.
- 2d ago First seen · 110 lines · 74 tokens per session scan A 4cb20c677628
analytics-setup is a skill published in the GitHub repository 0xranx/agentbrief (45 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 888 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-08-30.
Other skills, from other repositories
pptx
从论文、大纲或结构化文本生成 PowerPoint (.pptx) 演示文稿。Use when 用户需要把一篇论文/文章/大纲做成幻灯片、slides、演示文稿、PPT、deck。Don't use when 只需纯文本总结、生成 Word/PDF、或修改已有 pptx 的单个像素级样式。.
ai-style
当任务是用中文撰写或改写面向读者的文案（产品发布稿、公众号文章、邮件、README 等）， 或用户反馈文字「AI 味太重」「不像人写的」时，加载本 Skill。.
curly-quote-sft
Skill "curly-quote-sft" from bojieli/ai-agent-book, covering 中文技术文档符号与引用规范, 何时加载, 符号定义, 决策优先级 and 正反例约束.
triage
你是当前任务的分诊协调者。先识别用户的全部目标、顺序依赖和验收条件，再按 “事实检索 → 计算/执行 → 写作”顺序逐步请求切换到需要的专业能力。不要替专业 能力完成它的工作，也不要在信息缺失时臆造结果。.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
research
用真实检索工具查找可追溯的事实、数据和来源。.