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 jtrackingai/analytics-tracking-automation --skill tracking-verifygit clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automationWrote 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/jtrackingai/analytics-tracking-automation/tracking-verify)<a href="https://agentmods.dev/skills/jtrackingai/analytics-tracking-automation/tracking-verify"><img src="https://agentmods.dev/badge/skills/jtrackingai/analytics-tracking-automation/tracking-verify/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/jtrackingai/analytics-tracking-automation/tracking-verify"><img src="https://agentmods.dev/badge/skills/jtrackingai/analytics-tracking-automation/tracking-verify.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.00025 | $0.00586 |
| Opus 5.5 | $0.00010 | $0.00234 |
| Sonnet 5.5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
tracking-verify 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tracking Verify
Use this skill for verification and optional publish handoff.
Inputs
<artifact-dir>/event-schema.json<artifact-dir>/gtm-context.json
Workflow
If the telemetry consent prompt appears and no prior choice is recorded, stop and follow ../../references/telemetry-consent.md before continuing.
Run preview:
./event-tracking preview <artifact-dir>/event-schema.json --context-file <artifact-dir>/gtm-context.json
If comparing against an older preview run, pass the previous health baseline:
./event-tracking preview <artifact-dir>/event-schema.json --context-file <artifact-dir>/gtm-context.json --baseline <previous-tracking-health.json>
preview launches a real Chromium via Playwright and exercises the live site to fire GA4/GTM events for verification. Run it in an environment that permits outbound network and local browser execution; environments that restrict either tend to cause Playwright to hang or fail silently rather than return a clean error.
Then interpret:
- blockers
- expected failures
- selector mismatches
- unexpected fired events outside the approved schema
- release readiness
If the user explicitly wants to publish after verification:
./event-tracking publish --context-file <artifact-dir>/gtm-context.json --version-name "GA4 Events v1 - <date>"
If tracking-health.json is missing, still manual-only, or has blockers, publish now stops by default. Only use --force when the user explicitly wants to override that gate.
Required Output
Produce and share:
<artifact-dir>/preview-report.md<artifact-dir>/preview-result.json<artifact-dir>/tracking-health.json<artifact-dir>/tracking-health-report.md<artifact-dir>/tracking-health-history/- updated
<artifact-dir>/workflow-state.json
Closeout Style
- default to a verification verdict first: healthy, blocked, or manual follow-up required
- summarize blockers, unexpected events, and release-readiness in plain language before listing files
- keep raw preview data and artifact references after the summary
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.
- 1mo ago First seen · 78 lines · 25 tokens per session scan A cb3ef14f4465
tracking-verify is a skill published in the GitHub repository jtrackingai/analytics-tracking-automation (144 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 586 once invoked, about $0.0001 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
test-strategy-document
Create a production-ready Testing Strategy and QA Execution Plan. Covers testing levels (unit, integration, E2E, performance), mocking boundaries, test environment matrix, code coverage thresholds, and automated CI pipeline runsheets. Use when establishing a QA framework for a new system or feature set.
lifecycle-qa
Generate test event payloads for generated journeys — positive triggers, branch-condition cases, exits, and negative tests — so the CRM setup can be verified before launch. Use when the user says "test payload", "test eventi üret", "qa", "tetikleyiciyi test et", "sahte event".
verification-traceability
Make a declared design assertion checkable and traceable. Use when adding or changing a contract assertion, choosing how to verify a behaviour, or when a behaviour has no expected output.
xcode-testing-workflow
Guide Swift Testing, XCTest, XCUITest, XCUIAutomation-oriented mechanics, code coverage, xctestplan matrices, accessibility-verification follow-through, test filtering, retries, diagnostics, and test-specific fallback work in existing Xcode-managed projects and workspaces. Use when Xcode-aware execution is needed and…
starfleetctl-dev
Developing and deploying the starfleetctl source itself — claim protocol, make, bootstrap, daemon restarts in the right order, end-to-end verification. Load before editing anything in a starfleetctl source checkout, before running starfleet-bootstrap, or when a web/plugin change 'is done' but the fleet does not see it.
Forge
Autonomous quality engineering swarm that forges production-ready code through continuous behavioral verification, exhaustive E2E testing, and self-healing fix loops. Combines DDD+ADR+TDD methodology with BDD/Gherkin specifications, 7 quality gates, defect prediction, chaos testing, and cross-context dependency…