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-135-top-of-page-rate-monitoringgit 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-135-top-of-page-rate-monitoring)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-135-top-of-page-rate-monitoring"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-135-top-of-page-rate-monitoring/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-135-top-of-page-rate-monitoring"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-135-top-of-page-rate-monitoring.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.00026 | $0.00679 |
| Opus 5.5 | $0.00010 | $0.00272 |
| Sonnet 5.5 | $0.00005 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
skill-135-top-of-page-rate-monitoring 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 135: Top of Page Rate Monitoring
Purpose
Monitor top-of-page and absolute-top position rates to ensure ads appear in premium SERP positions that drive better CTR and conversions. Identify campaigns/keywords underperforming on position and recommend bid or QS improvements.
Data Requirements
Data Source: Custom GAQL Required
Position metrics require custom GAQL queries.
GAQL Query:
SELECT
campaign.name,
ad_group.name,
metrics.impressions,
metrics.clicks,
metrics.cost_micros,
metrics.conversions,
metrics.search_top_impression_share,
metrics.search_absolute_top_impression_share,
metrics.search_impression_share
FROM ad_group
WHERE campaign.advertising_channel_type = 'SEARCH'
AND campaign.status = 'ENABLED'
AND segments.date DURING LAST_30_DAYS
Run via /google-ads:get-custom with query name serp_position_metrics.
Analysis Steps
- Fetch position metrics: Run GAQL query for top IS metrics
- Calculate position rates: Top IS and Absolute Top IS by campaign/ad group
- Segment by position tier: Premium (>80%), Good (60-80%), Moderate (40-60%), Low (<40%)
- Correlate with performance: Compare CTR/conversion rate by position tier
- Identify improvement opportunities: Flag high-value entities with low top IS
Thresholds
| Condition | Severity |
|---|---|
| Brand campaign Top IS < 80% | Critical |
| High-value campaign Abs Top IS < 20% | Warning |
| Top IS declining >10% week-over-week | Warning |
| Non-brand campaign Top IS < 40% | Info |
Output
Short format (default):
## SERP Position Audit
**Account:** [Name] | **Campaigns:** [X] | **Low Position Issues:** [Y]
### Position Summary by Campaign
| Campaign | Top IS | Abs Top IS | Category |
|----------|--------|------------|----------|
| [Brand] | [X]% | [Y]% | Premium |
| [Product] | [X]% | [Y]% | Moderate |
### Position vs Performance
| Position Tier | Avg CTR | Avg Conv Rate |
|---------------|---------|---------------|
| Abs Top (>50%) | [X]% | [Y]% |
| Top (20-50%) | [X]% | [Y]% |
| Lower (<20%) | [X]% | [Y]% |
### Issues Requiring Attention
- **[Campaign]**: Top IS only [X]%, below target → Increase bids
- **Brand Campaign**: Abs Top IS dropped to [X]% → Investigate competition
### Recommendations
1. Increase bids on [campaigns] to improve top position
2. Improve QS to achieve top position more efficiently
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 · 89 lines · 26 tokens per session scan A bde60e00f9ec
skill-135-top-of-page-rate-monitoring is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 26 tokens to every session and 679 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…