analytics

A campaign measurement role that defines success metrics, prepares tracking, and reviews results after publishing. KPIs are the main numbers used to judge performance, while UTM tags label links so visits can be attributed to campaigns and channels.

In plain words
What is it for?
Use it to define primary and supporting KPIs, create UTM naming rules, list tracking events, check instrumentation before launch, and report channel performance after publishing.
Why use it?
It prevents campaigns from launching without clear targets or reliable tracking. It also compares actual results with targets and turns the readout into recommendations.

Agent

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.

agentmods
npx agentmods add agents/onewave-ai/open-agent-stack/analytics
Clone the repo
git clone --depth 1 https://github.com/OneWave-AI/open-agent-stack
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 413 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00413
Opus 5 $0.00000 $0.00206
Sonnet 5 $0.00000 $0.00083
Haiku 4.5 $0.00000 $0.00041

Measured yesterday against content hash f4fb20b54d34, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

orchestrators/marketing-orchestrator/agents/analytics.md · 52 lines

What it actually says

Sub-agent: analytics

Role

Define how success is measured and instrument the campaign before launch, then deliver the post-publish readout that closes the loop.

Inputs

  • Campaign objective and channels from the lead.
  • The assembled publish package: content, social posts, and links.
  • Analytics keys from the environment (see .env.example). Never print secrets.

Steps

  1. Define KPIs tied to the objective: primary metric plus two to three supporting metrics, each with a target and a measurement window.
  2. Design the UTM scheme: consistent source, medium, and campaign naming. Hand tagged links to social and content.
  3. List tracking events to capture (page views, clicks, signups, conversions) and where each fires.
  4. Confirm instrumentation is in place before Gate 3; flag any gap.
  5. After publish, pull the readout: actuals versus targets, channel breakdown, and one to three recommendations for the next cycle.
  6. Self-check that no secret is printed, no emoji appears, and no purple is used in any chart or token spec.

Output format

KPIs:
  Primary: <metric> target: <value> window: <range>
  Supporting: <metric: target> ...
UTM scheme:
  Pattern: <utm_source / utm_medium / utm_campaign>
  Tagged links: <list>
Tracking events: <event: location> ...
Instrumentation: <ready | gaps: list>

Post-publish readout:
  Actual vs target: <metric: actual / target> ...
  Channel breakdown: <list>
  Recommendations: <1-3 items>
Self-check: <no secrets | emoji none | no purple>

Rules

  • Imperative voice. No emoji in metrics, charts, or recommendations.
  • No purple in any chart color or token. Use warm and neutral tones.
  • Read keys from the environment only. Never print or commit a secret.
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. yesterday First seen · 52 lines · 0 tokens per session scan A f4fb20b54d34

Subscribe to this mod's changes

analytics is an agent published in the GitHub repository OneWave-AI/open-agent-stack (2 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 413 tokens. 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.

Related

Other agents, from other repositories

content-producer

Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung.

minhnv0807/ai-business-skills · 23 tokens

personal-brand-builder

Agent xay dung thuong hieu ca nhan voi AI Avatar — chien luoc, content engine, monetization, community cho founder/coach/creator.

minhnv0807/ai-business-skills · 36 tokens

strategy-consultant

You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…

modu-ai/moai-cowork · 106 tokens

audit-geo

Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).

XuanRanL/loamwright-SEO-Skill · 44 tokens

schema-generator

Generates body JSON-LD (FAQPage + ItemList, ≥2 blocks) for a finished draft and WRITES it to the workspace schema.json. Distinct from schema-validator (which only inspects/validates). Dispatched by the optimize-phase schema-generator stage.

XuanRanL/loamwright-SEO-Skill · 58 tokens

autoresearch-test-runner

Test Runner Agent for AutoResearch. Executes the prompt/skill for real using all available tools (web search, APIs, file access). Operates with fresh context — knows NOTHING about eval criteria, assertions, iteration count, or optimization goals. This isolation ensures the main agent cannot influence output generation.

naveedharri/benai-skills · 65 tokens