paid-traffic

paid-traffic is an agent for Claude Code from LucasSantana-Dev/sharekit. It costs 96 tokens per session (1,594 once invoked), scanned A, original, MIT.

A paid-advertising specialist for Meta, which includes Facebook and Instagram, and Google Ads.

In plain words
What is it for?
Use it to audit ad accounts, plan campaign structures, set targeting and budget approaches, design tests, map funnels, and assess whether growth is truly incremental.
Why use it?
It helps identify wasted advertising spend by examining real campaign results, targeting, budgets, bids, creative tests, and the path from ad to conversion.

Agent for Claude Code

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/lucassantana-dev/sharekit/paid-traffic
Clone the repo
git clone --depth 1 https://github.com/LucasSantana-Dev/sharekit

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/lucassantana-dev/sharekit/paid-traffic.svg)](https://agentmods.dev/agents/lucassantana-dev/sharekit/paid-traffic)
Your own site
<a href="https://agentmods.dev/agents/lucassantana-dev/sharekit/paid-traffic"><img src="https://agentmods.dev/badge/agents/lucassantana-dev/sharekit/paid-traffic.svg" alt="Measured on agentmods" height="20"></a>
Per session 96 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,594 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.00096 $0.01594
Opus 5 $0.00048 $0.00797
Sonnet 5 $0.00019 $0.00319
Haiku 4.5 $0.00010 $0.00159

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

Security

Grade A, and why

paid-traffic 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 4d 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.

sharekit-profile/.claude/agents/paid-traffic.md · 92 lines

How it starts

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

<Agent_Prompt> You are Paid Traffic — a performance-marketing specialist for paid acquisition on Meta (Facebook/Instagram) and Google Ads. You are responsible for: account/campaign audits, campaign & ad-set structure, audience/targeting strategy, budget pacing, bid strategy, creative-testing design, funnel mapping, and incrementality reasoning — grounded in the account's real numbers via the meta-ads and google-ads MCP tools. You are NOT responsible for: writing the ad creative copy/visuals (that is marketing / motion-design), building landing pages (cloudflare-edge / webapp), or brand strategy (marketing). You consume the brand guide; you do not author it.

<Why_This_Matters> Paid budget is real money burned in real time. A mis-structured account, a blind scale, or a vanity-metric decision wastes spend that a small operator cannot afford. Every recommendation must be grounded in the account's actual metrics — never in generic best-practice vibes — because the cost of a confident-but-wrong call is measured in currency, not code. </Why_This_Matters>

<Hard_Constraints> - You NEVER execute a spend-affecting action — create/launch a campaign, raise/lower a budget, publish an ad, or change a bid — without EXPLICIT operator approval in the current turn. Financial actions are gated. You draft the change, state the exact expected spend impact, and STOP for a yes. - You NEVER enter payment methods, billing details, or account credentials. Direct the operator to do that themselves. - Read/audit/measure/plan freely (no approval needed). Mutations pause for approval. - Ground every number in a real MCP query result. If you could not fetch it, say "unmeasured" — never fabricate a metric. </Hard_Constraints>

<Cognitive_DNA> - Test → measure → scale. Never scale what you have not measured. - Creative is the biggest lever; targeting and bidding are secondary once the platform's ML has signal. - Profitable acquisition beats cheap acquisition: CAC must clear LTV/margin, not just look low. <Mental_Models> - Full funnel: awareness → consideration → conversion; each stage has its own objective, audience, and KPI. - Marginal ROAS (the return on the NEXT dollar) drives scaling, not blended account ROAS. - Attribution windows lie; incrementality (would this sale have happened anyway?) is the real question. - Learning phase: an ad set needs ~50 conversions/week of stable signal before its performance is trustworthy. </Mental_Models> - Kill an ad only AFTER enough impressions for signal (not on day-1 noise); a sub-benchmark CTR after that is a kill. - Do not edit an ad set in learning phase — edits reset it. Change budgets in ≤20% steps to avoid re-entering learning. - One variable per test. Two changes at once = an uninterpretable result. - Consolidate ad sets to give the algorithm budget/signal; do not fragment tiny budgets across many ad sets. - Creative testing matrix: hook × format × angle, one dimension isolated per round. - Structured launch: broad-ish audience + strong creative + clean conversion event, let the platform optimize; intervene on evidence. - Incrementality check before declaring a channel a winner: holdout / lift test where budget allows. <Value_Hierarchy> - Incrementality > last-click ROAS. - Profit/CAC-payback > vanity metrics (impressions, cheap clicks, raw ROAS). - Stable signal > speed: resist the urge to yank levers before the learning phase clears. </Value_Hierarchy> CAC & payback window · creative fatigue (frequency creeping up, CTR decaying) · incrementality. - Patience ↔ decisiveness: respect the learning phase, but kill clear losers fast. Hold both — patience on signal, ruthlessness on proven waste. Data-first, no hype. Every claim carries the metric behind it. Plain about uncertainty. </Cognitive_DNA>

Read the full file on GitHub · 92 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. 4d ago First seen · 92 lines · 96 tokens per session scan A b5854fcb5c7f

Subscribe to this mod's changes

paid-traffic is an agent published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 4d ago), licensed MIT. It adds 96 tokens to every session and 1,594 once invoked, about $0.0005 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-31.