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-125-landing-page-health-check-automationgit 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-125-landing-page-health-check-automation)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-125-landing-page-health-check-automation"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-125-landing-page-health-check-automation/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-125-landing-page-health-check-automation"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-125-landing-page-health-check-automation.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.00607 |
| Opus 5.5 | $0.00012 | $0.00243 |
| Sonnet 5.5 | $0.00006 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
skill-125-landing-page-health-check-automation 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 125: Landing Page Health Check
Purpose
Extract all destination URLs from ads and keywords, then audit for technical issues (404 errors, slow load times, SSL problems, redirect chains) that waste ad spend and hurt Quality Score.
Data Requirements
Data Source: Standard + Custom GAQL
Standard Data:
data/account/campaigns/*/*/ads.md- Ad final URLsdata/account/campaigns/*/*/keywords.md- Keyword-level URLs (if present)
GAQL Query (for landing page performance):
SELECT
landing_page_view.unexpanded_final_url,
metrics.impressions,
metrics.clicks,
metrics.cost_micros,
metrics.conversions
FROM landing_page_view
WHERE segments.date DURING LAST_30_DAYS
ORDER BY metrics.clicks DESC
Run via /google-ads:get-custom with query name landing_page_performance.
Analysis Steps
- Extract URL inventory: Compile all unique final URLs from ads and keywords
- Fetch landing page metrics: Get performance data per URL via GAQL
- Identify high-traffic URLs: Prioritize URLs with significant spend/clicks
- Cross-reference with ad disapprovals: Check for destination-related policy issues
- Calculate wasted spend: Estimate cost on URLs with known issues
Thresholds
| Condition | Severity |
|---|---|
| 404/500 error on active URL | Critical |
| SSL certificate expired/invalid | Critical |
| Redirect chain > 3 hops | Warning |
| Load time > 5 seconds | Warning |
| Non-mobile-friendly with mobile traffic | Warning |
Output
Short format (default):
## Landing Page Health Audit
**Account:** [Name] | **URLs Checked:** [X] | **Issues:** [Y]
### Critical - Immediate Fix ([Count])
- **[URL]**: 404 error, [X] clicks wasted → Pause ads or fix URL
- **[URL]**: SSL expired → Renew certificate
### Warnings ([Count])
- **[URL]**: Redirect chain ([X] hops) → Update to final URL
- **[URL]**: Slow load ([X]s) → Optimize page speed
### Wasted Spend
$[Amount] spent on broken/problematic URLs in last 30 days
### Recommendations
1. Fix [X] broken URLs immediately
2. Reduce redirect chains on [Y] URLs
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 · 81 lines · 31 tokens per session scan A fb9a68b56ba5
skill-125-landing-page-health-check-automation 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 607 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
interactive-login
Log a CLI in with a browser/device-code flow (aws sso, gh, glab, gcloud, …) and save the result to the keychain so later commands can request it through execute.credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
azure-messaging-webpubsub-java
Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
open-design-browser
Inspect and exercise local HTML design artifacts and library prototype previews with the existing agent-browser CLI, including screenshots, interaction checks, and rendered DOM snapshots. Use when rendered evidence helps author or review a design; excludes browser installation, remote services, and unrelated browser…