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 ooiyeefei/ccc --skill google-analytics-setupgit clone --depth 1 https://github.com/ooiyeefei/cccWrote 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/ooiyeefei/ccc/google-analytics-setup)<a href="https://agentmods.dev/skills/ooiyeefei/ccc/google-analytics-setup"><img src="https://agentmods.dev/badge/skills/ooiyeefei/ccc/google-analytics-setup/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/ooiyeefei/ccc/google-analytics-setup"><img src="https://agentmods.dev/badge/skills/ooiyeefei/ccc/google-analytics-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Tool Misuse · line 95 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
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.00149 | $0.02038 |
| Opus 5.5 | $0.00060 | $0.00815 |
| Sonnet 5.5 | $0.00030 | $0.00408 |
| Haiku 4.5 | $0.00015 | $0.00204 |
Grade A, and why
google-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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Analytics 4 Setup
Get GA4 tracking a real conversion, verified end to end, so ad spend is measured against something trustworthy. GA4's model is different from old Universal Analytics, and the single most common failure is spending money before confirming the conversion event actually fires. This skill front-loads that.
Start where the user is
GA4 setup is a chain: account → property → data stream → tag on site → conversion event → mark as Key Event → verify. People arrive at different points in that chain. Guessing wastes their time and risks duplicate properties (which cannot be merged later). So always ask first what already exists, then jump in at the right link:
Ask (adapt to what they've said):
- Do you already have a Google Analytics account / property? If yes, what's it called?
- Do you have a data stream for this site yet, and a Measurement ID (looks like
G-XXXXXXXXXX)? If yes, paste it. - What's the one conversion that matters most (a waitlist/contact form submit, a signup, a purchase)? Everything downstream optimizes for this.
- What's the site — a framework (Next.js, plain HTML, WordPress, Shopify) and the domain? This decides how the tag goes in.
Then go straight to the relevant section below. Skip what they've already done. Do NOT re-create anything that exists.
Property and stream structure — decide once, correctly
Getting the hierarchy wrong fragments data permanently, so settle it before creating anything.
- A GA4 property is a hard reporting boundary. Data does not flow across properties (cross-property analysis needs BigQuery or paid GA360). So: one property per product, not per page, per feature, or per plan tier.
- A data stream is per domain, not per path. One web stream captures every path on that hostname automatically. A page like
/pricingor/waitlistdoes NOT get its own stream — it shares the site's stream, and you tell pages apart bypage_path. - Distinguish sub-parts inside one property with
page_path(automatic) or a custom dimension (e.g.plan_tier,product_area) on events — never with separate properties. - Only make a second stream for a genuinely different domain (e.g. a separate marketing site on its own hostname).
What ships with it
5 files 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.
- 1mo ago First seen · 111 lines · 149 tokens per session scan A dc5ccc45bcde
google-analytics-setup is a skill published in the GitHub repository ooiyeefei/ccc (496 stars, last pushed 2d ago), licensed MIT. It adds 149 tokens to every session and 2,038 once invoked, about $0.0006 per session on Opus 5.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
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…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.