A pre-launch checklist for a website or application. It runs build and rule checks, tests the site, checks search visibility, reviews performance and accessibility, checks secrets and environment settings, and records deployment steps.

Use it when preparing to deploy, launch, or decide whether a production build meets the project's technical and website requirements.

It exposes release problems before launch instead of assuming that a successful development build means the production site is ready.

How textura-agency/ai-design-vault configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to textura-agency/ai-design-vault. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/textura-agency/ai-design-vault/main/.claude/skills/ship-check/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/textura-agency/ai-design-vault

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/textura-agency/ai-design-vault/ship-check/github.svg)](https://agentmods.dev/skills/textura-agency/ai-design-vault/ship-check)

Your own site

<a href="https://agentmods.dev/skills/textura-agency/ai-design-vault/ship-check"><img src="https://agentmods.dev/badge/skills/textura-agency/ai-design-vault/ship-check/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/textura-agency/ai-design-vault/ship-check"><img src="https://agentmods.dev/badge/skills/textura-agency/ai-design-vault/ship-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,004 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00072	$0.01004
Opus 5.5	$0.00029	$0.00402
Sonnet 5.5	$0.00014	$0.00201
Haiku 4.5	$0.00007	$0.00100

Measured 23d ago against content hash d00752ac357b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ship-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 23d 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.

.claude/skills/ship-check/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ship check

Run in order. Anything unchecked is stated as unchecked in the summary — never assume a pass. Every command comes from .claude/stack.json → commands.

1. It builds and it obeys the rules

.claude/scripts/verify.sh        # zero FAILs
node -e 'const c=require("./.claude/stack.json").commands;console.log([c.lint,c.typecheck,c.build].filter(Boolean).join("\n"))'

Run each printed command. The build must pass with no warnings you cannot explain.

2. It is correct

Run the qa-verify skill across the site — every route, every breakpoint. Then click through the production build, not the dev server (commands.build then commands.start, or a preview deploy). Dev servers hide hydration errors, prerender gaps and asset-path mistakes.

3. It can be found

Run the seo-audit skill. Non-negotiable before launch:

the render model actually delivers content to crawlers (view-source, not devtools)
every public route is in the sitemap
robots allows crawling; no staging noindex survives
the site URL variable is set in the production environment
unique title + description per route; OG image resolves absolutely
Organization + WebSite JSON-LD renders and validates
if this replaces an existing site → the site-migration redirect map is live and verified

4. It is fast

Measure, do not guess — Lighthouse on the deployed URL, mobile profile.

LCP ≤ 2.5s, CLS ≤ 0.1, INP ≤ 200ms
Hero image priority-loaded; every image sized; fonts self-hosted or preloaded
Client JS per route is justified — nothing hydrating that did not need to
If a WebGL/three.js scene exists → the optimize-3d-scene skill first
Motion holds 60fps on a mid-range phone, not just a laptop

5. It is usable by everyone

Keyboard-only pass through every interactive element; focus always visible
prefers-reduced-motion honoured — content readable with motion off
Contrast AA; alt text everywhere; landmarks named
44px touch targets; no horizontal scroll at 320px

Read the full file on GitHub · 92 lines

Changes

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.

23d ago First seen · 92 lines · 72 tokens per session scan A d00752ac357b

Subscribe to this mod's changes

ship-check is a skill published in the GitHub repository textura-agency/ai-design-vault (25 stars, last pushed 2mo ago), licensed Unlicense. It adds 72 tokens to every session and 1,004 once invoked, about $0.0003 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-14.

Cloud DevOps and cloud Marketing and SEO

ship-check next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ship-checktextura-agency/ai-design-vault	Skill	25	2mo ago	Unlicense	A	72	Claude Code
gke-compute-classesgoogle/skills	Skill	22k	yesterday	Apache-2.0	A	83	Claude Code, Codex
gke-reliabilitygoogle/skills	Skill	22k	yesterday	Apache-2.0	A	85	Claude Code, Codex
gke-workload-securitygoogle/skills	Skill	22k	yesterday	Apache-2.0	A	171	Claude Code, Codex
cloud-architectJeffallan/claude-skills	Skill	12k	7d ago	MIT	A	71	Claude Code
nemo-automodel-launcher-configNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	30	Claude Code
azure-mgmt-botservice-dotnetmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	78	Claude Code

ai-design-vault: Skill for Claude Code