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-121-impression-share-lost-analysisgit 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-121-impression-share-lost-analysis)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-121-impression-share-lost-analysis"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-121-impression-share-lost-analysis/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-121-impression-share-lost-analysis"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-121-impression-share-lost-analysis.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.00030 | $0.00673 |
| Opus 5.5 | $0.00012 | $0.00269 |
| Sonnet 5.5 | $0.00006 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
skill-121-impression-share-lost-analysis 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 121: Impression Share Lost Analysis
Purpose
Analyze impression share loss to distinguish between budget-constrained campaigns (need more budget) and rank-constrained campaigns (need better Quality Score or bids). This prioritization ensures optimization efforts target the right root cause.
Data Requirements
Data Source: Custom GAQL Required
The standard export does not include competitive impression share metrics.
GAQL Query:
SELECT
campaign.name,
campaign.id,
campaign.status,
campaign_budget.amount_micros,
metrics.impressions,
metrics.clicks,
metrics.cost_micros,
metrics.conversions,
metrics.search_impression_share,
metrics.search_budget_lost_impression_share,
metrics.search_rank_lost_impression_share,
metrics.search_top_impression_share,
metrics.search_absolute_top_impression_share
FROM campaign
WHERE campaign.status = 'ENABLED'
AND campaign.advertising_channel_type = 'SEARCH'
AND segments.date DURING LAST_30_DAYS
Run via /google-ads:get-custom with query name impression_share_loss.
Analysis Steps
- Fetch impression share data: Run custom GAQL query to get IS metrics by campaign
- Categorize campaigns: Group by primary loss cause (Budget >10%, Rank >20%, Both, or Optimized)
- Calculate opportunity cost: Estimate missed impressions, clicks, and conversions from lost IS
- Diagnose root causes: For budget loss, check exhaustion time; for rank loss, check Quality Scores
- Prioritize recommendations: Rank by potential recovery value and effort required
Thresholds
| Condition | Severity |
|---|---|
| Budget Lost IS > 20% on profitable campaign | Critical |
| Rank Lost IS > 30% | Critical |
| Budget Lost IS > 10% | Warning |
| Rank Lost IS > 20% | Warning |
| Either metric > 5% but < 10% | Info |
Output
Short format (default):
## Impression Share Loss Audit
**Account:** [Name] | **Campaigns:** [X] | **Issues:** [Y]
### Critical ([Count])
- **[Campaign]**: [X]% lost to budget, profitable CPA $[Y] → Increase budget by $[Z]/day
- **[Campaign]**: [X]% lost to rank, avg QS [Y] → Improve landing page experience
### Warnings ([Count])
- **[Campaign]**: [X]% lost to [cause] → [Fix]
### Recommendations
1. Increase budget on [campaigns] to capture $[X] in missed conversions
2. Address QS issues on [campaigns] losing [X]% to rank
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 · 30 tokens per session scan A 58425a85c7ec
skill-121-impression-share-lost-analysis is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 30 tokens to every session and 673 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…