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-021-below-first-page-bidgit 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-021-below-first-page-bid)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-021-below-first-page-bid"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-021-below-first-page-bid/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-021-below-first-page-bid"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-021-below-first-page-bid.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.00658 |
| Opus 5.5 | $0.00010 | $0.00263 |
| Sonnet 5.5 | $0.00005 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
skill-021-below-first-page-bid 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 021: Below-First-Page Bid Identification
Purpose
Identify keywords where low bids are limiting visibility and performance. Keywords with very low impressions combined with good Quality Scores indicate bid-related issues rather than quality issues. Fixing these can unlock significant additional traffic.
Data Requirements
Data Source: Standard
Standard Data:
data/account/campaigns/*/*/keywords.md- Keyword bids and Quality Scoredata/performance/campaigns/*/*/keywords_metrics_30_days.md- Impressions and performancedata/account/campaigns/*/campaign.md- Campaign bidding strategy
Reference GAQL:
SELECT
campaign.name,
ad_group.name,
ad_group_criterion.keyword.text,
ad_group_criterion.keyword.match_type,
ad_group_criterion.cpc_bid_micros,
ad_group_criterion.quality_info.quality_score,
metrics.impressions,
metrics.average_cpc
FROM keyword_view
WHERE ad_group_criterion.status = 'ENABLED'
AND segments.date DURING LAST_30_DAYS
Use /google-ads:get-custom if you need impression share metrics for more accurate diagnosis.
Analysis Steps
- Identify low-impression keywords: Flag keywords with <100 impressions in 30 days or significantly below ad group average
- Analyze bid vs Quality Score: For low-impression keywords, check if QS is reasonable (5+) - suggests bid issue, not quality
- Calculate Ad Rank proxy: Compare Bid x QS across keywords in same ad group to find under-bidders
- Estimate bid adjustment needed: Use average CPC of performing keywords as benchmark (first-page estimate ~1.5-2x avg CPC)
- Prioritize by opportunity: Rank by QS (higher = more impact) and strategic importance
Thresholds
| Condition | Severity |
|---|---|
| Impressions < 50 AND QS >= 7 | Critical |
| Impressions < 100 AND QS >= 5 | Warning |
| Bid < 50% of ad group avg CPC AND QS >= 6 | Critical |
| Impressions < 200 AND QS < 5 | Info (quality issue) |
Output
Short (default):
## Below-First-Page Bid Audit
**Account:** [Name] | **Analyzed:** [X] keywords | **Issues:** [Y]
### Critical ([Count])
- **[Keyword]** (QS [X]): [Y] impressions, bid $[Z] vs $[A] avg CPC -> Increase to $[B]
### Warnings ([Count])
- **[Keyword]**: [Issue] -> [Fix]
### Recommendations
1. [Priority action with estimated 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 · 76 lines · 26 tokens per session scan A 5b5f6e988395
skill-021-below-first-page-bid 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 658 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…