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 agentmods add skills/viknesh20-20/claude-code-tool-kit/web-launch-checknpx skills add viknesh20-20/claude-code-tool-kit --skill web-launch-checkgit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/web-launch-check)<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/web-launch-check"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/web-launch-check.svg" alt="Measured on agentmods" 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 | $0.00071 | $0.01423 |
| Opus 5 | $0.00036 | $0.00711 |
| Sonnet 5 | $0.00014 | $0.00285 |
| Haiku 4.5 | $0.00007 | $0.00142 |
Grade A, and why
web-launch-check 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 4d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/web-launch-check
Run this before any production website launch to catch missing legal pages, broken SEO, accessibility violations, or compliance gaps that would expose the user to legal risk or hurt search ranking.
When to use
- Before pushing a marketing site, landing page, or web app to production.
- After a major redesign that changed page structure, routes, or third-party integrations.
- Before adding analytics or tracking scripts.
- When taking over an existing site to assess current state.
What it checks
Layer 1 — Legal pages (CRITICAL — block launch)
| Page | Path checked | Required when |
|---|---|---|
| Privacy Policy | /privacy, /privacy-policy, footer link |
Always (any data collection, including cookies/IP) |
| Terms of Service | /terms, /tos, /terms-of-service |
Any signup, transaction, or user-generated content |
| Cookie Policy | /cookies, section in /privacy |
EU/UK visitors, or any non-essential cookies |
| Contact / Address | /contact, footer |
EU jurisdictions (Impressum, EU consumer law); always recommended |
| Refund / Cancellation | /refunds, /cancellation |
Any e-commerce or paid product |
Layer 2 — Consent & tracking (HIGH)
- Cookie consent banner present before any non-essential cookie is set.
- Reject button as prominent as Accept.
- Tracking scripts (Google Analytics, Meta Pixel, etc.) blocked until consent.
- "Do Not Sell or Share" link if California users (CCPA/CPRA).
- Global Privacy Control signal honored.
Layer 3 — Sessions & auth (HIGH)
- Cookies have
Secure,HttpOnly,SameSite=Lax(orStrict). - Auth tokens not in
localStorageif long-lived. - Logout invalidates session server-side.
- CSRF protection on state-changing requests.
- Session expiry explicit; idle timeout for sensitive flows.
Layer 4 — SEO essentials (HIGH)
- Every page has unique
<title>(≤ 60 chars). - Every page has unique
<meta name="description">(~150 chars). - Every page has
<link rel="canonical">. - Every page has Open Graph tags (
og:title,og:description,og:image,og:url,og:type). - Every page has Twitter Card tags.
- Structured data (JSON-LD) where relevant (Organization, Article, Product, BreadcrumbList, FAQ).
<html lang>set.- Exactly one
<h1>per page; heading hierarchy correct. - Alt text on every meaningful image.
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.
- 4d ago First seen · 152 lines · 71 tokens per session scan A ee1e526ce57e
web-launch-check is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 1,423 once invoked, about $0.0004 per session on Opus 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-08-31.
Other skills, from other repositories
mcaf-nfr
Capture or refine non-functional requirements such as accessibility, reliability, scalability, maintainability, performance, and compliance. Use when a feature or architecture change needs explicit quality attributes and trade-offs.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
palette
Improving usability, interaction quality, cognitive load reduction, feedback design, and a11y compliance. Use when improving UX usability or interaction feel.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
ui-design-source
Use this skill when the user provides Figma material, design-export files, screenshots of design tools, PDFs, JSON, existing HTML, or asks for design-to-HTML/code fidelity. It adapts OpenDesign/Figma handoff discipline for UIDesigner without requiring a live Figma runtime.
ux-design
Create comprehensive UX design with user flows, wireframes, and design systems.