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 san-npm/skills-ws --skill google-analyticsgit clone --depth 1 https://github.com/san-npm/skills-wsWrote 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/san-npm/skills-ws/google-analytics)<a href="https://agentmods.dev/skills/san-npm/skills-ws/google-analytics"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/google-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/san-npm/skills-ws/google-analytics"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/google-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.00074 | $0.04641 |
| Opus 5 | $0.00037 | $0.02320 |
| Sonnet 5 | $0.00015 | $0.00928 |
| Haiku 4.5 | $0.00007 | $0.00464 |
Grade A, and why
google-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 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Analytics 4
Workflow
1. Measurement Plan
Before touching GA4, define what matters:
| Layer | Question | Example |
|---|---|---|
| Business objective | What's the goal? | Increase trial signups 20% |
| KPI | How do we measure? | Trial signup rate, activation rate |
| Events | What do we track? | sign_up, tutorial_complete, plan_selected |
| Dimensions | What context? | plan_type, referral_source, user_role |
2. Event Taxonomy
Use a consistent naming convention. Never use spaces or capitals in event names.
Naming pattern: object_action (noun_verb)
# Core events (auto-collected — don't recreate)
page_view, session_start, first_visit, user_engagement
# Recommended events (use GA4 standard names)
sign_up, login, purchase, add_to_cart, begin_checkout
# Custom events (your business logic)
trial_started
feature_activated
plan_upgraded
invite_sent
onboarding_completed
support_ticket_opened
Implementation (gtag.js):
// Custom event with parameters
gtag('event', 'trial_started', {
plan_type: 'pro',
referral_source: 'pricing_page',
value: 49
});
// User property (set once per user)
gtag('set', 'user_properties', {
account_type: 'enterprise',
company_size: '50-200'
});
GTM dataLayer push:
dataLayer.push({
event: 'plan_upgraded',
plan_from: 'free',
plan_to: 'pro',
mrr_delta: 49
});
3. GTM Implementation & Consent Mode v2
If you load GA4 through Google Tag Manager (web container), use exactly one GA4 base tag plus event tags — never also hardcode gtag.js for the same property (that is the #1 cause of doubled events).
Tag structure:
- Google tag (
G-XXXXXXX) — fires once on Initialization - All Pages (formerly the "GA4 Configuration" tag; renamed to the unified Google tag). Set shared fields/user properties here. - GA4 Event tags — one per custom event, triggered by a Custom Event trigger matching your
dataLayereventname. MapdataLayervalues into Event parameters (these become GA4 event params; register them as custom definitions — section 4 — to use them in reports). - Pass enhanced-measurement-overlapping events carefully; disable GA4 enhanced measurement options you are sending manually to avoid duplicates (e.g. don't send a manual
page_viewif enhanced measurement page views are on).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 327 lines · 74 tokens per session scan A 98500975e94d
google-analytics is a skill published in the GitHub repository san-npm/skills-ws (2 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 4,641 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-31.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…