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 reatlat/fullstory-claude-plugin --skill campaign-trackergit clone --depth 1 https://github.com/reatlat/fullstory-claude-pluginWrote 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/reatlat/fullstory-claude-plugin/campaign-tracker)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/campaign-tracker"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/campaign-tracker/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/reatlat/fullstory-claude-plugin/campaign-tracker"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/campaign-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.01433 |
| Opus 5 | $0.00022 | $0.00717 |
| Sonnet 5 | $0.00009 | $0.00287 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
campaign-tracker 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 11d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Campaign Tracker
Track marketing campaigns end-to-end — from UTM click to conversion, with cohort-level behavior analysis.
When to Use
- "How did the email campaign perform?"
- "Compare conversion rates across Facebook, Google, and email campaigns"
- "What do users from the Q3 product launch campaign do after landing?"
- "Which campaign has the best retention — users who convert and come back?"
- "Show me sessions from users who clicked the July newsletter"
- "Is paid search traffic converting better than organic?"
Mental Model
A campaign sends users to your site with tracking parameters (UTM tags). Fullstory captures the landing page URL including those parameters. By building segments from UTM values, you can track campaign cohorts through every page and action.
The campaign funnel:
- Click: User clicks the campaign link (happens outside Fullstory)
- Landing: User arrives on your site (first page view with UTM params)
- Engagement: User browses, interacts, explores
- Conversion: User completes the goal (purchase, signup, demo request)
Fullstory sees steps 2-4. Step 1 data comes from your marketing platform.
Workflow
Step 1: Identify campaign parameters
Ask the user for the UTM parameters they want to track:
utm_source(e.g., facebook, google, newsletter)utm_medium(e.g., cpc, email, social)utm_campaign(e.g., q3_launch, black_friday, summer_sale)utm_content(e.g., banner_a, hero_cta — for A/B testing creative)
Step 2: Build campaign segments
Build a segment for each campaign cohort:
fullstory:build_segment(
"users who first landed with utm_campaign=q3_launch in last 30 days"
)
For multi-campaign comparison, build one segment per campaign:
seg_q3_launch = "utm_campaign=q3_launch"
seg_black_friday = "utm_campaign=black_friday"
seg_newsletter = "utm_source=newsletter"
Step 3: Measure campaign performance
For each campaign, compute:
fullstory:build_metric(query="page views", output_type="single_number")
fullstory:update_metric(metric_id, segment_id)
fullstory:compute_metric(metric_id)
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.
- 11d ago First seen · 139 lines · 43 tokens per session scan A 5d2765d2fd20
campaign-tracker is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 28d ago), licensed MIT. It adds 43 tokens to every session and 1,433 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
roblox-input
Use when handling Roblox keyboard, mouse, gamepad, touch, motion input, or cross-platform action binding.
roblox-lighting
Use for Roblox lighting, atmosphere, day/night, or post-processing effects.
roblox-performance
Use when profiling Roblox performance or diagnosing FPS, memory, network, mobile, or hot-path problems.
roblox-growth-design
Use for growth diagnosis, discovery, retention, onboarding, experiments, LiveOps, and packaging.
roblox-networking
Use when validating RemoteEvent or RemoteFunction arguments, adding rate limits, designing server-authoritative systems, or preventing exploits.
roblox-ui-design
Use for Roblox UI composition, hierarchy, visual systems, style inheritance, accessibility, and design review.