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-156-first-party-data-collection-activation-strategygit 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-156-first-party-data-collection-activation-strategy)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-156-first-party-data-collection-activation-strategy"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-156-first-party-data-collection-activation-strategy/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-156-first-party-data-collection-activation-strategy"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-156-first-party-data-collection-activation-strategy.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.00031 | $0.00654 |
| Opus 5.5 | $0.00012 | $0.00262 |
| Sonnet 5.5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
skill-156-first-party-data-collection-activation-strategy 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 156: First-Party Data Collection and Activation Strategy
Purpose
Assess first-party data collection and activation for Google Ads targeting and measurement. As third-party cookies decline, first-party data becomes essential for Customer Match, Enhanced Conversions, offline conversion import, and audience creation.
Data Requirements
Data Source: Custom GAQL Required
Standard export doesn't include Customer Match audience configuration or match rates.
Reference GAQL (Customer Match Audiences):
SELECT
user_list.name,
user_list.type,
user_list.size_for_search,
user_list.size_for_display,
user_list.membership_status
FROM user_list
WHERE user_list.type = 'CRM_BASED'
Run via /google-ads:get-custom to inventory Customer Match lists.
Additional Data Sources:
- CRM system (Salesforce, HubSpot) - email counts, data quality
- E-commerce platform - customer records, transaction data
- Email marketing platform - subscriber counts, engagement data
- Google Ads Data Manager status
Analysis Steps
- Inventory data sources: Document all first-party data currently collected (CRM, e-commerce, email, loyalty)
- Assess data quality: Evaluate email validity rates, phone formatting, data recency
- Review activation status: Check Customer Match audiences, Enhanced Conversions, offline imports
- Identify collection gaps: Find missing collection points and low opt-in rates
- Evaluate privacy compliance: Verify consent mechanisms and data retention policies
Thresholds
| Condition | Severity |
|---|---|
| Enhanced Conversions not implemented | Critical |
| Customer Match lists stale (>30 days since refresh) | Critical |
| Match rate <50% on uploaded lists | Warning |
| CRM data available but not uploaded to Google Ads | Warning |
| Email capture rate <3% on key pages | Warning |
| No consent management for data collection | Info |
Output
Short format (default):
## First-Party Data Audit
**Account:** [Name] | **Data sources:** [X] | **Activation gaps:** [Y]
### Critical ([Count])
- **Enhanced Conversions**: Not implemented -> Enable for +5-10% conversion capture
- **Customer Match**: Last refresh [X] days ago -> Automate weekly sync
### Warnings ([Count])
- **[Data source]**: Available but not activated -> Upload to Google Ads
- **Match rate**: [X]% on [list] -> Improve data quality
### Data Inventory
| Source | Records | Quality | Activated |
|--------|---------|---------|-----------|
| CRM | X | High/Med/Low | Yes/No |
### Recommendations
1. [Specific activation with expected impact]
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 · 84 lines · 31 tokens per session scan A 2fb26fd8a64c
skill-156-first-party-data-collection-activation-strategy is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 31 tokens to every session and 654 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…