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 Ootto-AI/claude-content-skills --skill utm-campaign-plangit clone --depth 1 https://github.com/Ootto-AI/claude-content-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/ootto-ai/claude-content-skills/utm-campaign-plan)<a href="https://agentmods.dev/skills/ootto-ai/claude-content-skills/utm-campaign-plan"><img src="https://agentmods.dev/badge/skills/ootto-ai/claude-content-skills/utm-campaign-plan/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/ootto-ai/claude-content-skills/utm-campaign-plan"><img src="https://agentmods.dev/badge/skills/ootto-ai/claude-content-skills/utm-campaign-plan.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.00115 | $0.00625 |
| Opus 5 | $0.00057 | $0.00313 |
| Sonnet 5 | $0.00023 | $0.00125 |
| Haiku 4.5 | $0.00012 | $0.00063 |
Grade A, and why
utm-campaign-plan 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 12d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UTM Campaign Plan
Create a small, consistent link taxonomy that answers real reporting questions without turning every URL into ungoverned tracking noise.
1. Start with the reporting question
Ask what decision the data should support, which destinations are approved, which channels and partners are involved, what analytics system consumes the links, and what naming convention already exists. If no reporting owner or system is known, document that limitation before issuing links.
2. Define the controlled vocabulary
Set clear allowed values for source, medium, campaign, content, and term only when each has a decision use. Use human-readable, stable naming. Separate owned social, paid social, creators, partners, and experiments so later reporting does not blend unlike traffic.
3. Issue a link register
For every link, provide the destination, intended placement, UTM values, owner, start and end context, and approval status. Include examples and invalid examples. Reserve a process for changes so a creator or operator does not silently alter the taxonomy.
4. Validate before use and review after
Check that URLs resolve to the approved destination, parameters are encoded correctly, and the same source is not represented by several names. After the campaign, compare link usage against the register and record any taxonomy correction for the next brief.
Hard rules
- Do not create tracking links for unapproved destinations or campaigns.
- Never put personal data, sensitive information, customer names, or private identifiers in UTM values.
- Do not treat UTM tags as proof of conversion or causation.
- Preserve existing analytics conventions unless an authorised owner approves a change.
- Keep affiliate, paid, organic, creator, and partner traffic distinguishable.
Failure modes
| Failure | Do this instead |
|---|---|
| Every team member invents names | Publish one controlled vocabulary and a shared register. |
| Parameters contain personal or sensitive data | Use a non-identifying campaign label and keep sensitive data out of URLs. |
| A short link hides an unverified destination | Validate the final redirect and approved landing page before sharing. |
| Reports blend creator and paid traffic | Assign separate medium/source values and preserve them in the register. |
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.
- 12d ago First seen · 46 lines · 115 tokens per session scan A 24c5d9c39d01
utm-campaign-plan is a skill published in the GitHub repository Ootto-AI/claude-content-skills (30 stars, last pushed 20d ago), licensed MIT. It adds 115 tokens to every session and 625 once invoked, about $0.0006 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
scrapecreators-api
Scrape and extract public data from 27+ social media platforms using the ScrapeCreators REST API. Covers TikTok, Instagram, YouTube, LinkedIn, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, Snapchat, Twitch, Kick, Truth Social, TikTok Shop, Google, and link-in-bio services (Linktree, Komi, Pillar, Linkbio…
outlier-post-finder
Use when the user wants to find posts, videos, reels, shorts, tweets, or social content that overperformed versus a creator, brand, or competitor baseline. Finds outliers, explains why they worked, extracts hooks and formats, and produces a practical swipe file.
ad-library-teardown
Use when the user wants to analyze active ads from Meta/Facebook, Google, or LinkedIn ad libraries; tear down a competitor's messaging; extract hooks, offers, CTAs, video transcripts, landing page claims, and test ideas from public ads.
comment-mining
Use when the user wants to mine comments and replies for audience reactions, customer language, questions, objections, complaints, product ideas, buying intent, sentiment, or voice-of-customer insights from public social posts and videos.
competitor-social-research
Use when the user wants to research competitors' social media strategy, compare brands or creators, find what content is working in a niche, identify content gaps, or produce a practical social strategy brief from public social data.
transcript-intelligence
Use when the user wants to summarize, analyze, or repurpose transcripts from TikTok, Instagram, YouTube, Facebook, X/Twitter, LinkedIn, Rumble, or Reddit video posts. Extracts hooks, claims, quotes, content atoms, themes, and reusable scripts.