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 skills add SkeneTechnologies/plg-skills --skill product-analyticsgit clone --depth 1 https://github.com/SkeneTechnologies/plg-skillsWrote 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/skenetechnologies/plg-skills/product-analytics)<a href="https://agentmods.dev/skills/skenetechnologies/plg-skills/product-analytics"><img src="https://agentmods.dev/badge/skills/skenetechnologies/plg-skills/product-analytics/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/skills/skenetechnologies/plg-skills/product-analytics"><img src="https://agentmods.dev/badge/skills/skenetechnologies/plg-skills/product-analytics.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.00085 | $0.03451 |
| Opus 5 | $0.00043 | $0.01725 |
| Sonnet 5 | $0.00017 | $0.00690 |
| Haiku 4.5 | $0.00009 | $0.00345 |
Grade A, and why
product-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 11d 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 — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Analytics
You are a product analytics specialist. Set up and operationalize a product analytics system designed for PLG insights. This skill covers event taxonomy design, analytics tool selection, implementation best practices, and analysis frameworks that turn raw product data into growth decisions.
Diagnostic Questions
Before designing your analytics system, answer:
- What questions do you need to answer? (List the top 10 questions your team asks about user behavior)
- What analytics tools do you currently use? (And what are you dissatisfied with?)
- What is your technical stack? (Web, mobile, backend language, data warehouse)
- How many active users do you have? (Affects tool pricing and data volume planning)
- Who will consume analytics? (Engineers only, product managers, executives, marketing?)
- What is your privacy posture? (GDPR, CCPA, SOC 2, data residency requirements)
- Do you have a data warehouse? (Snowflake, BigQuery, Redshift, Databricks)
- What is your budget for analytics tooling?
Codebase Audit (Optional)
If you have access to the user's codebase, analyze it before asking diagnostic questions. Use findings to pre-fill answers and focus recommendations on what actually exists.
- Find analytics SDKs: Search for imports of
mixpanel,amplitude,posthog,segment,@segment/analytics-next,ga4,gtag,rudderstack,heap - Find tracking calls: Search for
track(,capture(,logEvent(,gtag('event',analytics.track(,posthog.capture( - List all tracked events: Extract event names from tracking calls -- build an inventory of what's currently tracked
- Check user identification: Search for
identify(,setUserId(,setUserProperties(,people.set( - Find tracking initialization: Search for analytics init/setup code -- check if properly configured with API keys
- Check for a tracking plan: Look for files like
events.ts,analytics.ts,tracking.ts,events.jsonthat define event schemas - Find page/screen tracking: Search for
page(,screen(,pageview, route change tracking - Check for server-side tracking: Search backend code for analytics calls -- not just client-side
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.
- 11d ago First seen · 414 lines · 85 tokens per session scan A 640d35b85ad2
product-analytics is a skill published in the GitHub repository SkeneTechnologies/plg-skills (19 stars, last pushed 7mo ago), licensed MIT. It adds 85 tokens to every session and 3,451 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…