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-145-prelaunch-compliance-checklistgit 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-145-prelaunch-compliance-checklist)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-145-prelaunch-compliance-checklist"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-145-prelaunch-compliance-checklist/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-145-prelaunch-compliance-checklist"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-145-prelaunch-compliance-checklist.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.00028 | $0.00624 |
| Opus 5.5 | $0.00011 | $0.00250 |
| Sonnet 5.5 | $0.00006 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
skill-145-prelaunch-compliance-checklist 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 145: Pre-Launch Compliance Checklist
Purpose
Provide a systematic pre-launch review checklist to catch policy violations before ads go live. Prevents disapprovals, delays, and potential strikes by ensuring all ads meet Google Ads policy requirements.
Data Requirements
Data Source: Standard (for comparison)
Standard Data:
data/account/campaigns/*/*/ads.md- Existing approved ads (for reference)data/account/ext_*.md- Extension templates
This skill is primarily a checklist guide rather than data analysis.
Analysis Steps
- Check prohibited content: Verify product/service is allowed
- Review editorial standards: Check headlines and descriptions for formatting
- Verify claims: Ensure all claims are substantiated
- Audit landing page: Confirm destination compliance
- Check targeting alignment: Verify audience/content appropriateness
- Review extensions: Validate extension compliance
Thresholds
| Condition | Severity |
|---|---|
| Prohibited content detected | Critical |
| Restricted content without certification | Critical |
| Unsubstantiated claim ("Best", "#1") | Warning |
| Editorial issue (caps, punctuation) | Warning |
| Landing page missing required elements | Warning |
Output
Short format (default):
## Pre-Launch Compliance Checklist
**Campaign:** [Name] | **Ads to Review:** [X]
### Prohibited Content Check
| Check | Status |
|-------|--------|
| Not counterfeit goods | [ ] Pass |
| Not dangerous products | [ ] Pass |
| Not enabling dishonest behavior | [ ] Pass |
| No adult content | [ ] Pass |
### Editorial Standards
| Check | Status | Issue |
|-------|--------|-------|
| No excessive CAPS | [ ] Pass/Fail | [Detail] |
| No gimmicky punctuation | [ ] Pass/Fail | [Detail] |
| Correct spelling | [ ] Pass/Fail | [Detail] |
| Proper grammar | [ ] Pass/Fail | [Detail] |
### Claims Verification
| Claim | Type | Substantiated |
|-------|------|---------------|
| "[Claim]" | Price | [ ] Yes/No |
| "[Claim]" | Comparison | [ ] Yes/No |
### Landing Page Compliance
| Requirement | Status |
|-------------|--------|
| URL accessible | [ ] Pass |
| SSL valid | [ ] Pass |
| Privacy policy present | [ ] Pass |
| Content matches ad | [ ] Pass |
### Launch Decision
[ ] APPROVED - All checks passed
[ ] CONDITIONAL - Fix noted issues first
[ ] NOT APPROVED - Critical violations
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 · 90 lines · 28 tokens per session scan A 1018cb5de891
skill-145-prelaunch-compliance-checklist is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 22d ago), licensed MIT. It adds 28 tokens to every session and 624 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…