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 petrkindlmann/qa-skills --skill analytics-tracking-testinggit clone --depth 1 https://github.com/petrkindlmann/qa-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/petrkindlmann/qa-skills/analytics-tracking-testing)<a href="https://agentmods.dev/skills/petrkindlmann/qa-skills/analytics-tracking-testing"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/analytics-tracking-testing/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/petrkindlmann/qa-skills/analytics-tracking-testing"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/analytics-tracking-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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 MCP Rug Pull · line 311 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00209 | $0.06082 |
| Opus 5.5 | $0.00084 | $0.02433 |
| Sonnet 5.5 | $0.00042 | $0.01216 |
| Haiku 4.5 | $0.00021 | $0.00608 |
Grade A, and why
analytics-tracking-testing 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 yesterday.
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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Route
| Situation | Go to |
|---|---|
| Assert one GA4 event fired with correct params | Intercepting GA4 beacons |
| Treat the tracking plan as a validated contract | The Tracking Plan Is the Contract |
| Verify dataLayer.push shape (not the beacon) | Asserting dataLayer.push |
| Pixel + server CAPI deduplication (event_id) | Pixels and Server-Side Deduplication |
| Events must/mustn't fire by consent state | Consent Mode v2 Gating |
| Capture every pixel in one reusable fixture | references/capture-fixture.md |
| News-media: article-view, scroll-depth, paywall | News-Media Events |
| Fail the build on a tracking regression | Regression-Gating in CI |
| Hundreds of events, many domains, small team | Buy vs Build |
Discovery Questions
First: check .agents/qa-project-context.md in the project root and skip anything it already answers (stack, tag manager, consent platform, target environments).
- Which tracking destinations are live? GA4 (
/g/collect), Meta Pixel (facebook.com/tr), TikTok (analytics.tiktok.com), LinkedIn (px.ads.linkedin.com), ad-tech tags — each has a different endpoint grammar, so the capture helper must know them all. - GTM or hardcoded gtag? GTM means the truth flows through
window.dataLayer.pushfirst, then GTM fires the beacon. You may assert at the push layer (input contract) AND the beacon (output contract); they are different tests. - Is there a tracking plan? If not, build one first — it is the contract everything else validates against. No plan means no objective pass/fail.
- Consent platform and default consent state? Consent Mode v2 changes which beacons are even allowed to fire before consent. You need the CMP's accept/reject selectors to drive the test.
- Client + server (CAPI) dedup in play? If purchases fire both client Pixel and server Conversions API, the
event_idmust match or you double-count. This is the correctness property, not "did fbq run." - News-media surface? Article pages add article-view, scroll-depth thresholds (25/50/75/100), and paywall-meter events that generic e-commerce plans miss.
What ships with it
8 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.
- yesterday Changed · +24 lines c7ac584777f3
- 1mo ago First seen · 343 lines · 209 tokens per session scan A 0b7069459ce7
analytics-tracking-testing is a skill published in the GitHub repository petrkindlmann/qa-skills (199 stars, last pushed today), licensed MIT. It adds 209 tokens to every session and 6,082 once invoked, about $0.0008 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
CI Pipeline Optimizer
Optimize CI test pipelines through intelligent test splitting, parallelization, caching strategies, and selective test execution based on code changes.
Flaky Test Quarantine
Detect, quarantine, and systematically fix flaky tests with automated retry analysis, root cause categorization, and CI pipeline integration for test reliability.
CI/CD Pipeline Advanced
Expert-level CI/CD pipeline skill for test automation. Covers GitHub Actions, Jenkins, GitLab CI, Azure DevOps, parallel execution, matrix strategies, caching, artifact management, and deployment gates.
Checkly Monitoring as Code
Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.
CI Test Sharding Parallelization
Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.
platform-engineering
Use this skill when building or operating internal developer platforms: infrastructure as code, CI/CD, container orchestration, service networking, secrets, and observability, or when shaping platform products, self-service interfaces, adoption evidence, and policy guardrails. Do not use it to define release process…