performance-tracking

performance-tracking is a skill for Claude Code, Codex from gtmagents/gtm-agents. It costs 19 tokens per session (308 once invoked), scanned A, original, Apache-2.0.

A measurement framework for tracking live campaigns through metrics, data sources, dashboards, alerts, and review routines.

In plain words
What is it for?
Use it to define metrics, connect advertising and customer data, create dashboards, set alerts, and record optimization decisions.
Why use it?
It brings campaign results into one view and helps teams notice falling conversions, overspending, or missed targets sooner.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to define metrics, connect advertising and customer data, create dashboards, set alerts, and record optimization decisions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gtmagents/gtm-agents/performance-tracking
Install

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.

Any agent
npx skills add gtmagents/gtm-agents --skill performance-tracking
Clone the repo
git clone --depth 1 https://github.com/gtmagents/gtm-agents

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for performance-tracking

README.md
[![agentmods](https://agentmods.dev/badge/skills/gtmagents/gtm-agents/performance-tracking/github.svg)](https://agentmods.dev/skills/gtmagents/gtm-agents/performance-tracking)
Your own site
<a href="https://agentmods.dev/skills/gtmagents/gtm-agents/performance-tracking"><img src="https://agentmods.dev/badge/skills/gtmagents/gtm-agents/performance-tracking/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.

agentmods 80×15 button for performance-tracking

Your own site · 80×15
<a href="https://agentmods.dev/skills/gtmagents/gtm-agents/performance-tracking"><img src="https://agentmods.dev/badge/skills/gtmagents/gtm-agents/performance-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 308 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00308
Opus 5 $0.00010 $0.00154
Sonnet 5 $0.00004 $0.00062
Haiku 4.5 $0.00002 $0.00031

Measured 8d ago against content hash b08dc18eb7a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

performance-tracking 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.

plugins/campaign-orchestration/skills/performance-tracking/SKILL.md · 33 lines

What it actually says

Performance Tracking Skill

When to Use

  • Before launch to define metrics, data sources, and reporting cadence.
  • During active campaigns to monitor pacing vs goals and trigger optimizations.
  • Post-campaign retros to capture learnings and benchmarks.

Framework

  1. Metric Hierarchy – define business (pipeline, revenue), leading (MQL, CTR), and diagnostic metrics (CPC, landing page CVR).
  2. Data Plumbing – map sources (ad platforms, MA, CRM, BI) and ensure consistent IDs/UTMs.
  3. Dashboard Build – create executive + operator views with automated refresh.
  4. Alerting – set thresholds for spend pacing, CPA, conversion drops, SLAs.
  5. Insight Cadence – daily standups, weekly deep dives, end-of-campaign retros.
  6. Documentation – record hypotheses, experiments, and outcomes.

Templates

  • KPI tree worksheet.
  • Dashboard spec (dataset, visualization, owner, refresh schedule).
  • Optimization log (date, insight, action, result).

Tips

  • Automate alert routing (Slack, email) so anomalies are actioned quickly.
  • Pair dashboards with narrative summaries to help execs interpret shifts.
  • Capture experiment context in the optimization log to prevent repeating failed tests.
  • Align BI/RevOps early so new metrics get logged before launch.

Changes

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.

  1. 8d ago First seen · 33 lines · 19 tokens per session scan A b08dc18eb7a4

Subscribe to this mod's changes

performance-tracking is a skill published in the GitHub repository gtmagents/gtm-agents (399 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 308 once invoked, about $0.0001 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-09-03.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens