launch

launch is a skill for Claude Code, Codex from aimeos/pagible. It costs 51 tokens per session (1,047 once invoked), scanned A, original, MIT.

A design system for building SaaS and startup landing pages. SaaS means software sold as an online service; the system covers page layout, colours, responsive themes, product sections, pricing, FAQs, and related content.

In plain words
What is it for?
Use it to build a marketing site with light and dark modes, product screenshots, feature sections, pricing, changelog, FAQ, and testimonials.
Why use it?
It removes the need to define a landing-page visual language and structure from scratch. It provides consistent guidance for presenting a product and its supporting information.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to build a marketing site with light and dark modes, product screenshots, feature sections, pricing, changelog, FAQ, and testimonials.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aimeos/pagible/launch
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 aimeos/pagible --skill launch
Clone the repo
git clone --depth 1 https://github.com/aimeos/pagible

Made for: Claude Code, Codex.

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 launch

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/aimeos/pagible/launch"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,047 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.01047
Opus 5.5 $0.00020 $0.00419
Sonnet 5.5 $0.00010 $0.00209
Haiku 4.5 $0.00005 $0.00105

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

Security

Grade A, and why

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

themes/launch/SKILL.md · 49 lines

How it starts

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

Launch Theme Design System

Direction

Use a confident, precise and calm layout like the best product sites (Linear, Vercel, Stripe, Resend): lots of whitespace, one clear message per section and the product itself as the main visual. Lead with the outcome for the user, show the product right below the hero, then prove it with customer logos, features, numbers and testimonials, and close with pricing, questions and a call to action. Show real product screenshots or clean UI mockups; avoid generic stock photos of people pointing at screens, abstract 3D blobs and decorative illustrations without meaning.

Foundations

  • Use only the markup and classes supplied by ./theme/views/.
  • Use system fonts (Inter or Geist if installed) with tight letter-spacing on headings, monospace for dates and code, and the existing --pico-* variables.
  • Keep page content within a 1200px maximum width and text sections within 46rem.
  • Use zinc neutrals (#09090B, #3F3F46, #71717A, #FAFAFA) for text and surfaces, indigo (#4F46E5, #A5B4FC in dark mode) for links, primary buttons and glows, and the indigo to violet to cyan gradient only for accents in headlines (*...*), icon tiles and figures.
  • Support light and dark mode; never place fixed light colors on themeable backgrounds.
  • Use 0.75rem corners, pill-shaped buttons and badges and thin borders instead of heavy shadows.

Components

  • Hero: centered text with a pill eyebrow for news ("New: …"), a headline of at most eight words with an accent in *...*, one sentence of text, a primary and a secondary action, and a wide 16:10 product screenshot in files.
  • Logos: cards in the badges layout with company names and optional monochrome logos directly below the hero.
  • Features: cards in three columns with six items form a bento grid; give the 1st and 4th card a longer text because they span two columns, and use white line icons as SVG images.
  • Feature details: image-text with grid-end/grid-start alternating, a screenshot, an H2 with an accent, a sentence and three bullet points starting with a bold keyword.
  • Figures: cards in the figures layout with four short numbers (uptime, customers, speed, rating).
  • Testimonials: six quotes with name, role and company and round portraits; put the strongest quote first.
  • Pricing: three or four plans with monthly and yearly prices (same unit values in every plan), a free plan, one highlighted plan with the badge "Most popular" and an enterprise plan with "Custom" and a "Talk to sales" link. For checkout, set access, url and price id, kind, interval, currency and reference. Follow with a comparison table and questions about billing.
  • Changelog: a vertical timeline with dates as labels, the release as title and Markdown bullet lists with the changes, newest first.
  • FAQ: six questions with short, direct answers about the free plan, billing, data storage and discounts.
  • Call to action: one cta before the footer with a headline accent, a short sentence and two buttons.
  • Footer: cards with a short product blurb first, then product, company and legal links; the layout adds the status link, notice and copyright.
  • Product details: the product config adds the SoftwareApplication JSON-LD, the announcement bar, "Sign in" and "Get started" in the header and the status pill in the footer.

Read the full file on GitHub · 49 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. 4d ago First seen · 49 lines · 51 tokens per session scan A aa536713fdfc

Subscribe to this mod's changes

launch is a skill published in the GitHub repository aimeos/pagible (596 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 1,047 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

strapi-cms

Customisable headless CMS with Strapi.

bidewio/better-openclaw · 13 tokens

payload

Use when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.

payloadcms/payload · 43 tokens

api-integration-architect

Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.

sickn33/agentic-awesome-skills · 33 tokens

scalar-design-system

Scalar's design system — design tokens, theming (@scalar/themes), CSS variables, and the @scalar/components library. Use when designing or implementing Scalar UI, especially with Paper (code-to-design / design-to-code), so output matches real Scalar tokens, colors, typography, spacing, and components instead of…

scalar/scalar · 68 tokens

lap

LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…

Lap-Platform/LAP · 89 tokens

api-connector-builder

Use when writing a client for someone else's REST or GraphQL API: auth flow choice and token refresh, pagination to exhaustion, retry-with-jitter on transient failures only, rate-limit-aware throttling. NOT inbound callbacks (that is webhooks), NOT chaining services (that is automation-flows), NOT designing your own…

ericrisco/rsc-harness · 80 tokens