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 taboola/realize-claude-plugin --skill manage-campaignsgit 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/manage-campaigns)<a href="https://agentmods.dev/skills/taboola/realize-claude-plugin/manage-campaigns"><img src="https://agentmods.dev/badge/skills/taboola/realize-claude-plugin/manage-campaigns.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.1 | $0.00180 | $0.10803 |
| Opus 5 | $0.00090 | $0.05402 |
| Sonnet 5 | $0.00036 | $0.02161 |
| Haiku 4.5 | $0.00018 | $0.01080 |
Grade A, and why
manage-campaigns 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.
How it starts
The opening of the file, as written. The whole thing — 509 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Campaigns
Writes for Realize campaigns and native + display items via MCP. Every destructive call is gated behind a preview and an explicit user confirmation; the preview always identifies the target account by name and opaque account_id. This skill is the only place in the plugin that calls the MCP write tools.
Depth: the full field-by-field MCP write-surface reference (every scalar on create_campaign, every field on create_native_item / create_display_item, per-strategy bid-lever gates, common payload patterns, failure modes) lives in references/mcp-write-surface.md. Read it when a payload needs detailed field coverage or when debugging a write rejection.
When to use
Trigger on any of: create, make, set up, launch, edit, update, change, pause, resume, duplicate, clone, delete, remove, bump the budget, raise the bid, lower CPC, swap the creative, add an ad, add a creative, target X, exclude Y.
If the user is asking about a campaign rather than changing it, route to the campaigns skill (reads only). If the user is diagnosing performance, route to optimize-campaign — that skill hands write prescriptions back here.
Prerequisites
account_idresolved via theaccountsskill. If missing, hand off there first.- For updates, the relevant
get_campaign/get_itemread MUST precede the write — both to render a diff preview and (forupdate_campaigntargeting blocks) to merge client-side so the full-replace semantics do not wipe dimensions the user didn't mention.
Tools this skill wraps
| Tool | Required params | Idempotent? | Notes |
|---|---|---|---|
mcp__realize-mcp__create_campaign |
account_id, name, marketing_objective, branding_text, spending_limit_model, bid_strategy |
No | Atomic. Ships PAUSED unless is_active=true. 15 optional targeting blocks (full-replace within block). |
mcp__realize-mcp__update_campaign |
account_id, campaign_id |
Yes | Scalars partial-merge; targeting blocks full-replace within a section. At least one updatable field required. |
mcp__realize-mcp__create_native_item |
account_id, campaign_id, url, title, description, thumbnail_url |
No | Optional branding_text, cta. New items typically PENDING_APPROVAL → RUNNING. |
mcp__realize-mcp__update_native_item |
account_id, campaign_id, item_id |
Yes | At least one updatable field required. |
mcp__realize-mcp__create_display_item |
account_id, campaign_id, url, creative_name, plus either ad_tag (3P JS) or asset_url + dimensions (1P-hosted) |
No | Locks campaign as Display on first call when pricing_model=CPC. 3P tags must match the validator allowlist (no <!DOCTYPE> / <html> wrapper). |
mcp__realize-mcp__update_display_item |
account_id, campaign_id, item_id |
Yes | At least one updatable field required. Arrays like verification_pixel are full-replace. |
mcp__realize-mcp__create_conversion_rule |
account_id, display_name, event_name, type, category, condition, look_back_window, include_in_total_conversions, status, effects |
No | Account-level. No tool-side defaults — every required field must be supplied. type / category / event_name immutable afterwards. Returns the server-assigned id. |
mcp__realize-mcp__update_conversion_rule |
account_id, rule_id |
Yes | Partial-merge on every field, including condition and effects — omitted fields keep their stored value. The only way to retire a rule (status=DISABLED / ARCHIVED); there is no delete tool. |
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.
- 4d ago Changed · +86 lines · +33 tokens per session 654a6872ca3d
- 8d ago First seen · 423 lines · 147 tokens per session scan A ea65fdb18505
manage-campaigns is a skill published in the GitHub repository taboola/realize-claude-plugin (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 180 tokens to every session and 10,803 once invoked, about $0.0009 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…