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/discoverynpx skills add taboola/realize-claude-plugin --skill discoverygit 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/discovery)<a href="https://agentmods.dev/skills/taboola/realize-claude-plugin/discovery"><img src="https://agentmods.dev/badge/skills/taboola/realize-claude-plugin/discovery.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.00059 | $0.01729 |
| Opus 5 | $0.00030 | $0.00864 |
| Sonnet 5 | $0.00012 | $0.00346 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
discovery 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery
Resolve opaque IDs and enumerate the catalogs that Realize's targeting / audience / publisher / conversion settings draw from. This skill wraps the nine read-only "look it up" tools the MCP exposes, so the user does not have to guess country codes, audience IDs, publisher IDs, segment IDs, CTA enum values, or IANA time zone names.
When to use
Trigger on any of:
- "What countries / regions / DMAs / cities / postal codes can I target?"
- "What operating systems / browsers does Realize support?"
- "What audiences / lookalike audiences / contextual segments are available on account X?"
- "List publishers on account X" / "Find publishers matching "
- "What conversion rules are configured on account X?"
- "What time zones does Realize support?"
- "What CTA button types are available for native items?"
- Any campaign-creation walkthrough where the user needs to paste an opaque ID rather than a display name.
For pulling performance numbers, route to the reports skill instead. For campaign/item lookup, route to the campaigns skill.
Prerequisites
account_idresolved via theaccountsskill is required for every tool below exceptsearch_geos,search_techno,list_time_zones, andlist_cta_types(those are global catalogs).
Tools this skill wraps
| Tool | Required params | Optional params | Returns |
|---|---|---|---|
mcp__realize-mcp__search_geos |
dimension ∈ {countries, regions, dma, cities, postal_codes} |
country_code (ISO-2 — required when dimension ≠ countries) |
{dimension, values: [{code, name}, ...]} |
mcp__realize-mcp__search_techno |
dimension ∈ {operating_system_versions, browsers} |
os_family (required when dimension=operating_system_versions) |
{dimension, values: [...]} |
mcp__realize-mcp__search_audiences |
account_id |
country_codes (comma-separated ISO-2), country_targeting_type ∈ {ALL, INCLUDE, EXCLUDE} |
Audience list with audience_id, name, ... |
mcp__realize-mcp__search_lookalike_audiences |
account_id |
country_code (ISO-2) |
Lookalike rules with rule_id, ... |
mcp__realize-mcp__search_contextual_segments |
account_id |
country_codes, country_targeting_type |
Segments with segment_id, ... |
mcp__realize-mcp__search_publishers |
account_id, query (use "*" for all) |
publisher_ids (array of int), page (default 1), page_size (max 50, default 10) |
Paginated publisher list {id, name, account_id, country, is_active} |
mcp__realize-mcp__search_conversion_rules |
account_id |
— | Conversion rules with id, ... |
mcp__realize-mcp__list_time_zones |
— | — | Array of IANA time zone names (e.g., America/New_York) |
mcp__realize-mcp__list_cta_types |
— | — | Array of valid cta_type enum values |
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 · 76 lines · 59 tokens per session scan A 8c77caa481cc
discovery is a skill published in the GitHub repository taboola/realize-claude-plugin (3 stars, last pushed 4d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,729 once invoked, about $0.0003 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…