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-074-server-side-tagging-assessmentgit 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-074-server-side-tagging-assessment)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-074-server-side-tagging-assessment"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-074-server-side-tagging-assessment/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-074-server-side-tagging-assessment"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-074-server-side-tagging-assessment.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.00525 |
| Opus 5.5 | $0.00010 | $0.00210 |
| Sonnet 5.5 | $0.00005 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
skill-074-server-side-tagging-assessment 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 074: Server-Side Tagging Assessment
Purpose
Evaluate the readiness and benefit of migrating from client-side to server-side tagging. Server-side tagging improves data accuracy, reduces page load impact, and provides better control over data flowing to advertising platforms.
Data Requirements
Data Source: Standard (plus external assessment)
Standard Data:
data/account/conversion_actions.md- Conversion tracking setupdata/account/account_summary.md- Account configuration
Note: Full server-side tagging assessment requires website/infrastructure access beyond Google Ads data.
Reference GAQL:
SELECT
conversion_action.name,
conversion_action.type,
conversion_action.origin
FROM conversion_action
WHERE conversion_action.status = 'ENABLED'
Use /google-ads:get-custom to check conversion action origins.
Analysis Steps
- Assess current tracking: Review conversion action types and origins (website tag, import, etc.).
- Identify benefit triggers: High ad blocker impact, page speed issues, privacy requirements.
- Evaluate readiness: GTM usage, development resources, infrastructure availability.
- Recommend approach: Migration priority based on benefits vs. effort.
Thresholds
| Condition | Severity |
|---|---|
| GDPR/CCPA strict requirements + no server-side | Critical |
| Estimated >20% tracking loss to ad blockers | Critical |
| Page speed heavily impacted by tags (>500ms) | Warning |
| No server-side tagging but high traffic | Warning |
| Simple tracking setup, low traffic | Info (may not need) |
Output
Short (default):
## Server-Side Tagging Assessment
**Account:** [Name] | **Recommendation:** [Proceed/Wait/Not Needed]
### Current State
| Factor | Status | Impact |
|--------|--------|--------|
| Tracking method | [Client-side/Server-side] | - |
| Privacy requirements | [High/Medium/Low] | [Assessment] |
| Estimated ad blocker impact | [%] | [Assessment] |
### Critical ([Count])
- **[Issue]**: [Description] -> [Fix]
### Recommendations
1. [Priority action]
2. [Secondary action]
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 · 77 lines · 25 tokens per session scan A babd71cb47b3
skill-074-server-side-tagging-assessment 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 525 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".