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 TrueClicks/claude-plugins --skill skill-104-customer-match-list-managementgit clone --depth 1 https://github.com/TrueClicks/claude-pluginsWrote 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/trueclicks/claude-plugins/skill-104-customer-match-list-management)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-104-customer-match-list-management"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-104-customer-match-list-management/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.
<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-104-customer-match-list-management"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-104-customer-match-list-management.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.00546 |
| Opus 5.5 | $0.00010 | $0.00218 |
| Sonnet 5.5 | $0.00005 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
skill-104-customer-match-list-management 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 21d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 104: Customer Match List Management
Purpose
Audit Customer Match list usage for cross-device targeting and lookalike creation. Customer Match is the most durable targeting signal as third-party cookies decline.
Data Requirements
Data Source: Custom GAQL Required
GAQL Query:
SELECT
user_list.name,
user_list.id,
user_list.type,
user_list.size_for_display,
user_list.size_for_search,
user_list.membership_status,
user_list.match_rate_percentage
FROM user_list
WHERE user_list.type = 'CRM_BASED'
Run via /google-ads:get-custom with query name customer_match_lists.
Standard Data:
data/account/campaigns/*/audience_targeting.md- Audience usage
Analysis Steps
- Identify Customer Match Lists: Find CRM-based lists in account
- Assess List Coverage: Check if key segments exist (all customers, high-value, recent)
- Evaluate Freshness: Identify stale lists (>30-90 days since update)
- Review Application Strategy: Verify lists used for targeting, exclusion, or lookalikes
Thresholds
| Condition | Severity |
|---|---|
| No Customer Match lists in account | Critical |
| Customer Match list <1,000 matched users | Warning |
| List not updated in >90 days | Warning |
| Lists exist but not applied to campaigns | Warning |
| No high-value customer segment | Info |
Output
Short (default):
## Customer Match List Audit
**Account:** [name] | **CM Lists:** [count] | **Applied:** [count] | **Issues:** [count]
### Critical
- **No Customer Match lists** - Upload customer email list
### Warnings
- **[list] not updated in [X] days** - Refresh weekly/monthly
- **[list] only [X] matched users** - Below 1,000 minimum
### Recommendations
1. Upload all customer emails (target: 10,000+)
2. Create high-value customer segment (top 20% LTV)
3. Set up weekly automated refresh from CRM
Detailed adds:
- Customer Match inventory table with sizes and match rates
- List application strategy by campaign type
- Recommended list structure (all, high-value, recent, lapsed)
- Compliance checklist
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.
- 21d ago First seen · 75 lines · 25 tokens per session scan A 0149718eae40
skill-104-customer-match-list-management is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 25 tokens to every session and 546 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-10-08.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…