froggo-mission-control: Skill for Claude Code

.claude/skills/paid-campaign-launch/SKILL.md

paid-campaign-launch is a skill for Claude Code from ProfFroggo/froggo-mission-control. It costs 37 tokens per session (2,763 once invoked), scanned A, original, Apache-2.0.

Pre-launch checklist and process for paid campaigns across Google, Meta, X, and Reddit — from creative approval to first-24h monitoring and kill-switch criteria.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: positional $N argument.

This is ProfFroggo/froggo-mission-control's own configuration. It tells Claude Code how to work on froggo-mission-control itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything froggo-mission-control configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ProfFroggo/froggo-mission-control. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ProfFroggo/froggo-mission-control/dev/.claude/skills/paid-campaign-launch/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ProfFroggo/froggo-mission-control

Made for: Claude Code.

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 paid-campaign-launch

README.md
[![agentmods](https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/paid-campaign-launch/github.svg)](https://agentmods.dev/skills/proffroggo/froggo-mission-control/paid-campaign-launch)
Your own site
<a href="https://agentmods.dev/skills/proffroggo/froggo-mission-control/paid-campaign-launch"><img src="https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/paid-campaign-launch/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 paid-campaign-launch

Your own site · 80×15
<a href="https://agentmods.dev/skills/proffroggo/froggo-mission-control/paid-campaign-launch"><img src="https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/paid-campaign-launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,763 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.00037 $0.02763
Opus 5.5 $0.00015 $0.01105
Sonnet 5.5 $0.00007 $0.00553
Haiku 4.5 $0.00004 $0.00276

Measured today against content hash b3f8efcca625, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

paid-campaign-launch 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 today.

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.

.claude/skills/paid-campaign-launch/SKILL.md · 271 lines

How it starts

The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

Launch paid campaigns that are tracking-clean, compliance-safe, structurally sound, and actively monitored from the moment they go live. A campaign that launches without verified tracking is worse than no campaign — it burns budget with no signal.

Trigger Conditions

Load this skill when:

  • Launching a new paid campaign on any platform
  • Resuming a paused campaign after creative or audience changes
  • Auditing an existing campaign for structural or compliance issues
  • Building a new campaign structure from scratch
  • Generating a post-launch performance report

Procedure

Step 1 — Pre-Launch Readiness Check

Complete every item before touching the platform launch button. Do not skip items. Do not launch with any box unchecked.

Tracking
  • Conversion pixel/tag confirmed firing on all target conversion events (test with Tag Assistant or Pixel Helper)
  • UTM parameters present and correct on all destination URLs
  • UTM format follows platform naming convention (see conventions below)
  • Landing page loads correctly from ad click (test click-through from preview)
  • Analytics tool (Mixpanel/GA4/internal) receiving test events
  • Conversion window configured appropriately (7-day click / 1-day view is standard for crypto products)
Audience
  • Target audience defined: demographics, interests, exclusions
  • Custom audiences uploaded or synced (if using CRM lists)
  • Lookalike audiences validated (check source audience size ≥ 1,000)
  • Exclusion audiences applied: existing customers excluded unless re-engagement campaign
  • Geographic targeting confirmed and legal in all targeted regions
  • Age gate applied where required (crypto ads: 18+ mandatory in all platforms)
Creative
  • All ad creatives reviewed and approved (internal approval record exists)
  • Creative dimensions correct for each placement (see specs below)
  • Copy reviewed for compliance (see platform-specific notes below)
  • No promises of guaranteed returns, no specific ROI claims
  • Disclaimers present where required by platform policy
  • Brand voice and visual standards applied

Read the full file on GitHub · 271 lines

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. today First seen · 271 lines · 37 tokens per session scan A b3f8efcca625

Subscribe to this mod's changes

paid-campaign-launch is a skill published in the GitHub repository ProfFroggo/froggo-mission-control (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 2,763 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-11-07.

Related

paid-campaign-launch compared with skills from other repositories

paid-campaign-launch next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
paid-campaign-launchProfFroggo/froggo-mission-controlSkill26mo agoApache-2.0A37Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143ktodayMITA103Claude Code