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 agentmods add skills/taboola/realize-claude-plugin/optimize-campaignnpx skills add taboola/realize-claude-plugin --skill optimize-campaigngit clone --depth 1 https://github.com/taboola/realize-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/taboola/realize-claude-plugin/optimize-campaign)<a href="https://agentmods.dev/skills/taboola/realize-claude-plugin/optimize-campaign"><img src="https://agentmods.dev/badge/skills/taboola/realize-claude-plugin/optimize-campaign.svg" alt="Measured on agentmods" 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 | $0.00105 | $0.04013 |
| Opus 5 | $0.00053 | $0.02006 |
| Sonnet 5 | $0.00021 | $0.00803 |
| Haiku 4.5 | $0.00011 | $0.00401 |
Grade A, and why
optimize-campaign 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 3d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimize Campaign
Data-driven diagnosis and recommendation loop for a Realize campaign. Pulls performance data via the MCP, applies mandatory pre-checks, then routes to one of two diagnostic paths and prescribes concrete next actions.
Internal vs user-facing terminology — never leak the framework names
The framework labels in this file ("pre-checks P1–P5", "RCA — 6-signal framework", "Signal 1 / Signal 2 / Signal 6", "residual signal", "creative restructure shock") are internal scaffolding for the model. Never surface them in user-facing output. Per os/guardrails.md, do the work and describe the actual finding in plain English.
| Internal label (this file uses) | What to say to the user |
|---|---|
| "mandatory pre-checks" / "running P1–P5" | Just do the checks silently. If a check matters to the answer, describe the finding ("the campaign has no conversion goal attached"). |
| "RCA — root cause analysis" (without expansion) | Either say "root cause analysis" in full, or just present the analysis. Don't label the process. |
| "Signal 1 (config change) → Signal 2 (supply concentration) chain" | Describe the actual sequence: "The Feb 13 block redirected spend to Yahoo Homepage, which then served lower-engagement slots — that's what shows up as the CTR drop." |
| "silent failure mode" / "silent diagnostic-quality killer" | Describe what's wrong factually: "The campaign doesn't have a conversion goal attached, so the optimizer doesn't know what to bid toward." No "silent" anything. |
| "residual signal — never the default" | Don't surface the framework hierarchy. Just present the conclusion. |
The framework helps you think; the user needs the conclusion, not the framework.
Depth: The substantive depth (dimensional drill-down rules, supply-side eligibility, creative-fatigue tiers, bid-lever matrix, symptom-class branches, common-mistake table, output discipline) lives in references/optimization-flow.md. Read it when a branch fires that needs operational specifics.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 190 lines · 105 tokens per session scan A d7c0710be0f6
optimize-campaign is a skill published in the GitHub repository taboola/realize-claude-plugin (3 stars, last pushed 4d ago), licensed Apache-2.0. It adds 105 tokens to every session and 4,013 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…