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 MithunWijayasiri/dotclaude --skill html-landing-pagegit clone --depth 1 https://github.com/MithunWijayasiri/dotclaudeWrote 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/mithunwijayasiri/dotclaude/html-landing-page)<a href="https://agentmods.dev/skills/mithunwijayasiri/dotclaude/html-landing-page"><img src="https://agentmods.dev/badge/skills/mithunwijayasiri/dotclaude/html-landing-page/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/mithunwijayasiri/dotclaude/html-landing-page"><img src="https://agentmods.dev/badge/skills/mithunwijayasiri/dotclaude/html-landing-page.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.00056 | $0.00999 |
| Opus 5.5 | $0.00022 | $0.00400 |
| Sonnet 5.5 | $0.00011 | $0.00200 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
html-landing-page 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 19d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HTML Landing Page
Landing-page layer on top of frontend-design:frontend-design.
Precedence
- Invoke
frontend-design:frontend-designvia Skill tool first, unless already loaded this session. It owns: grounding, plan → self-check → build → critique passes, AI-default looks, typography, motion budget, copy voice, general quality floor, screenshot critique. - This file adds only static-landing-page specifics. frontend-design updates far more often than this file → never restate or override its guidance here.
- Conflict on design taste → frontend-design wins. Conflict on landing-page constraints (checkpoint, copy verification, assets, deploy, Quality floor below) → this file wins.
- Editing this skill: before adding a rule, check frontend-design doesn't already cover it; delete rules here once it does.
Modes
- Build — new page → full Process.
- Review — existing page → audit against frontend-design's AI-default list, Landing-page tells, Quality floor, copy accuracy (Process step 6). Report findings, most severe first. Wait for go-ahead before changing anything.
- Redesign — Review, then run Process only on what failed; keep what passes.
Process
Runs inside frontend-design's passes; adds these steps.
- Mine the project. Read real material first: files, structure, vernacular, concrete numbers, command strings. Distinctive choices come from the subject's own world.
- Extend the plan. Beyond frontend-design's token plan, add:
- Signature: the ONE element the page is remembered by; must embody something true about the subject.
- Contrast: every text/bg pair ≥ 4.5:1 (body), ≥ 3:1 (large text, UI). Distinctive palettes fail this most often.
- Theme: light-only, dark-only, or follows
prefers-color-scheme. State it — otherwise it gets decided by accident.
- Checkpoint. Show plan (palette, type, layout sketch, signature, theme); wait for approval before writing HTML. Skip only if user said to build without review. Plan changes are cheap; built-page changes aren't.
- Build to the approved plan.
- Render. Open page in a browser; screenshot at ~375px and ~1280px; check console for errors. Judge screenshots, not source — overflow, spacing, and specificity bugs only show rendered.
- Verify copy. Check every factual claim against project source. Plausible-but-false → cut.
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.
- 19d ago Changed · -7 lines 497f22810260
- 25d ago Changed · +3 lines · -3 tokens per session ccd745196f37
- 2mo ago First seen · 72 lines · 59 tokens per session scan A 8bc618fd726d
html-landing-page is a skill published in the GitHub repository MithunWijayasiri/dotclaude (4 stars, last pushed 3d ago), licensed MIT. It adds 56 tokens to every session and 999 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-08-31.
Other skills, from other repositories
okhp3-replit-design-pipeline
The complete Replit design iteration loop as a single coherent workflow — extract → sandbox → variant → graduate. Use when redesigning, improving, or creating variants of any UI component or page. Covers the "extract first, never approximate" rule, DESIGN subagent brief anatomy, variant labelling conventions on…
design-system-specification
Design a production-ready Design System and UI/UX visual style guide. Covers design tokens (colors, typography, spacing, shadows, radius), components (buttons, inputs, cards, tables, modals, navigation), layouts, interaction/hover states, iconography, motion design, responsive behavior, accessibility (WCAG 2.2), and…
premium-frontend-ui
A comprehensive guide for GitHub Copilot to craft immersive, high-performance web experiences with advanced motion, typography, and architectural craftsmanship.
web-design-reviewer
This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage…
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
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".