prelaunch-checklist

prelaunch-checklist is a skill for Claude Code from teamniteo/hakuto. It costs 133 tokens per session (3,500 once invoked), scanned A, original, MIT.

A report-only checklist for checking whether a Hakuto website is ready to launch. It reviews configuration, forms, legal pages, placeholder text, search-engine checks, and required manual Cloudflare steps.

In plain words
What is it for?
Use it to inspect a site before release and receive lists of critical problems, warnings, passed checks, and manual tasks.
Why use it?
It helps find launch risks before publishing without changing the project files.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the AskUserQuestion tool.

Part of the hakuto plugin — 14 skills, 1 command, 1 agent shipped together

Good fit Use it to inspect a site before release and receive lists of critical problems, warnings, passed checks, and manual tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/teamniteo/hakuto/prelaunch-checklist
Install

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.

Any agent
npx skills add teamniteo/hakuto --skill prelaunch-checklist
Clone the repo
git clone --depth 1 https://github.com/teamniteo/hakuto

Made for: Claude Code.

Or install hakuto, the plugin that ships this one along with the rest of its 14 skills, 1 command, 1 agent.

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.

agentmods badge for prelaunch-checklist

README.md
[![agentmods](https://agentmods.dev/badge/skills/teamniteo/hakuto/prelaunch-checklist/github.svg)](https://agentmods.dev/skills/teamniteo/hakuto/prelaunch-checklist)
Your own site
<a href="https://agentmods.dev/skills/teamniteo/hakuto/prelaunch-checklist"><img src="https://agentmods.dev/badge/skills/teamniteo/hakuto/prelaunch-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.

agentmods 80×15 button for prelaunch-checklist

Your own site · 80×15
<a href="https://agentmods.dev/skills/teamniteo/hakuto/prelaunch-checklist"><img src="https://agentmods.dev/badge/skills/teamniteo/hakuto/prelaunch-checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 133 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,500 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00133 $0.03500
Opus 5 $0.00067 $0.01750
Sonnet 5 $0.00027 $0.00700
Haiku 4.5 $0.00013 $0.00350

Measured 8d ago against content hash 5e88c0570fc4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

prelaunch-checklist scanned grade A with 1 finding 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 8d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **Enable Markdown for Agents** (Cloudflare dashboard → AI Crawl Control → Markdown for Agents, or `dash.cloudflare.com/?to=/:account/:zone/ai`). Cloudflare converts HTML to markdown on the fly for clients sending `Acce
skills/prelaunch-checklist/SKILL.md · 279 lines

How it starts

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

Prelaunch Checklist Skill

Validate a Hakuto site is ready to go live. Report findings only — user requests fixes separately.

Run when the user says any of:

  • "Run prelaunch checklist"
  • "Is the site ready to ship?"
  • "Pre-launch check"
  • "Check before launch"

Execution Flow

1. Read project files in parallel

Read these into context up front:

  • wrangler.toml
  • package.json
  • src/layouts/Layout.astro
  • src/components/Footer.astro (if it exists; otherwise glob src/components/*Footer*)
  • astro.config.mjs

Glob for:

  • src/pages/privacy.*, src/pages/terms.*, src/pages/cookies.* (any extension)
  • src/components/**/*Form*.astro, src/components/**/*Form*.tsx
  • src/pages/**/*.astro (for the form scan in check #4)
  • worker/index.js (for form handler in check #4)

2. Initialize trackers

critical = []
warnings = []
passed = []
manual_reminders = []
gates = []   # SEO + source-review confirmations

3. Run automated checks

Check 1 — wrangler.toml customized

In wrangler.toml:

  • name = 'hakuto-site' → critical: "wrangler.toml name is still the scaffold default. Change to your project's worker name."
  • main missing → critical
  • All [[routes]] blocks still commented out AND no other custom-domain config → warning: "No custom domain in wrangler.toml. If you plan to use a custom domain via routes, uncomment the [[routes]] block. (Skip this if you're configuring the domain in the Cloudflare dashboard instead.)"
  • Otherwise → pass
Check 2 — compatibility_date freshness

Parse compatibility_date in wrangler.toml. If older than 12 months from today → warning: "compatibility_date is X months old; consider bumping for newer Workers runtime features."

Check 3 — package.json name

In package.json, if "name": "hakuto-site" → warning: "package.json name is still the scaffold default."

Check 4 — Forms wired

Grep src/ for <form (case-insensitive). For each match:

  • Find the enclosing component file.
  • Inspect the form's submission target (action attribute, fetch URL in script, or worker handler reference).
  • Critical if any of:
    • action="#" or action="" or action="/api/placeholder" or similar dummy values
    • Submits via fetch("/api/...") to a path that has no corresponding handler in worker/index.js
    • Recipient email/destination is a placeholder ([email protected], your-email@, [email protected])
  • Pass if a real endpoint and real recipient are wired.

Read the full file on GitHub · 279 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.

  1. 8d ago First seen · 279 lines · 133 tokens per session scan A 5e88c0570fc4

Subscribe to this mod's changes

prelaunch-checklist is a skill published in the GitHub repository teamniteo/hakuto (5 stars, last pushed 7d ago), licensed MIT. It adds 133 tokens to every session and 3,500 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens