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-141-landing-page-policy-compliancegit 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-141-landing-page-policy-compliance)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-141-landing-page-policy-compliance"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-141-landing-page-policy-compliance/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-141-landing-page-policy-compliance"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-141-landing-page-policy-compliance.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.00688 |
| Opus 5.5 | $0.00010 | $0.00275 |
| Sonnet 5.5 | $0.00005 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
skill-141-landing-page-policy-compliance 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 141: Landing Page Policy Compliance
Purpose
Audit destination URLs for Google Ads policy compliance requirements including privacy policy presence, SSL certificates, mobile-friendliness, and content alignment with ads. Non-compliant pages cause ad disapprovals and hurt Quality Score.
Data Requirements
Data Source: Standard + Custom GAQL
Standard Data:
data/account/campaigns/*/*/ads.md- Final URLs from adsdata/account/campaigns/*/*/keywords.md- Keyword-level URLs
GAQL Query (for landing page inventory):
SELECT
campaign.name,
ad_group.name,
ad_group_ad.ad.final_urls,
ad_group_ad.ad.final_mobile_urls,
ad_group_ad.policy_summary.approval_status
FROM ad_group_ad
WHERE ad_group_ad.status = 'ENABLED'
Run via /google-ads:get-custom with query name landing_page_urls.
Analysis Steps
- Extract URL inventory: Compile unique final URLs from ads and keywords
- Check technical compliance: SSL, accessibility, mobile-friendliness
- Verify content requirements: Privacy policy, contact info, business name
- Cross-reference disapprovals: Match URLs to destination-related policy issues
- Prioritize fixes: Order by traffic volume and policy risk
Thresholds
| Condition | Severity |
|---|---|
| Missing privacy policy on high-traffic URL | Critical |
| SSL certificate invalid or expired | Critical |
| 404 error on active landing page | Critical |
| Missing contact information | Warning |
| Slow load time (>5 seconds) | Warning |
| Non-mobile-friendly page | Warning |
Output
Short format (default):
## Landing Page Policy Audit
**Account:** [Name] | **URLs Audited:** [X] | **Compliance Issues:** [Y]
### Compliance Summary
| Requirement | Compliant | Issues |
|-------------|-----------|--------|
| Privacy Policy | [X] | [Y] |
| SSL Certificate | [X] | [Y] |
| Contact Info | [X] | [Y] |
| Mobile-Friendly | [X] | [Y] |
### Critical Issues
- **[URL]**: Missing privacy policy → Add to footer
- **[URL]**: SSL expired → Renew certificate
### Warnings
- **[URL]**: No contact info → Add phone/email
- **[URL]**: Slow load time → Optimize page
### Compliance Checklist
| Domain | Privacy | SSL | Contact | Mobile |
|--------|---------|-----|---------|--------|
| example.com | Yes | Valid | Yes | Yes |
| example2.com | No | Valid | No | Yes |
### Recommendations
1. Add privacy policy to [X] landing pages
2. Fix SSL on [Y] URLs
3. Add contact info to [Z] pages
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 · 93 lines · 26 tokens per session scan A 5f2f81b3580a
skill-141-landing-page-policy-compliance 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 688 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
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
ai-risk-management
Apply the NIST AI Risk Management Framework (AI RMF 1.0) and adjacent guidance to AI / ML systems — model lifecycle governance, fairness and bias evaluation, robustness, transparency, accountability, third-party model risk, monitoring for drift, and AI incident response. Broader than prompt-injection (which is the…