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 divyanshu-iitian/agent-website-design-skills --skill landing-page-craftgit clone --depth 1 https://github.com/divyanshu-iitian/agent-website-design-skillsWrote 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/divyanshu-iitian/agent-website-design-skills/landing-page-craft)<a href="https://agentmods.dev/skills/divyanshu-iitian/agent-website-design-skills/landing-page-craft"><img src="https://agentmods.dev/badge/skills/divyanshu-iitian/agent-website-design-skills/landing-page-craft/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/divyanshu-iitian/agent-website-design-skills/landing-page-craft"><img src="https://agentmods.dev/badge/skills/divyanshu-iitian/agent-website-design-skills/landing-page-craft.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.00063 | $0.00642 |
| Opus 5 | $0.00032 | $0.00321 |
| Sonnet 5 | $0.00013 | $0.00128 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
landing-page-craft 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 12d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page Craft
Build a page around a real decision, not a stack of fashionable sections. Make the offer understandable, believable, and actionable before adding polish.
Workflow
- Inspect existing brand, product, audience, traffic source, content, analytics requirements, and technical constraints.
- Write a one-line conversion brief:
- audience;
- situation or intent;
- offer and concrete outcome;
- primary action;
- biggest objection.
- Inventory available proof: product UI, examples, customer evidence, metrics, founder expertise, policies, integrations, security, or process. Never fabricate proof.
- Choose a page argument. Sequence only the sections needed to move the audience from recognition to confidence to action.
- Design the first viewport to answer:
- What is this?
- Is it for me?
- What changes if it works?
- What should I do next?
- Write concrete copy before tuning layout. Make headings informative, CTAs destination-aware, and claims proportional to evidence.
- Select a visual direction that belongs to the offer. Use product UI, real work, relevant imagery, data, or interaction as proof - not generic atmosphere.
- Implement semantic, responsive, performant UI in the project's existing stack. Include important loading, error, form, and success states.
- Place proof and risk-reversal near the decisions they support. Do not dump every trust signal into one logo wall.
- Verify the complete action path on mobile and desktop, including keyboard use, form validation, destinations, and tracking hooks when present.
Page Rules
- The H1 should communicate the offer or outcome; it does not have to repeat the brand name.
- Keep one primary action per decision point. Secondary actions should reduce uncertainty.
- Use real content and realistic lengths early enough to expose layout problems.
- Avoid section-count theater, repeated feature-card grids, fake testimonials, fake scarcity, and unsupported superlatives.
- Do not hide material price, renewal, privacy, eligibility, or cancellation information.
- Keep important content available without requiring decorative animation.
- Treat performance, accessibility, and responsive behavior as conversion features.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 56 lines · 63 tokens per session scan A 206e0af2c019
landing-page-craft is a skill published in the GitHub repository divyanshu-iitian/agent-website-design-skills (2 stars, last pushed 21d ago), licensed MIT. It adds 63 tokens to every session and 642 once invoked, about $0.0003 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
brand-visual-language
A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…
micro-interactions
Micro-interactions are small, purposeful animations and responses that reward the user and make the interface feel alive — an animated icon, a satisfying toggle, a subtle reveal. Borrowed from the natural world, they add delight without distraction. Use when designing interactive components, success states, toggles…
elevation-and-depth
Elevation — subtle shadows and layering — communicates visual hierarchy by lifting elements above the surface. Combined with border-radius, it creates the tactile quality of cards, modals, and interactive surfaces. Use when designing cards, dropdowns, modals, tooltips, or any floating UI element.
loading-states-and-perceived-performance
Manage user expectations during wait times with appropriate loading states — from simple spinners to complex skeleton screens and staggered animations. Perceived performance is often more important than actual load time. Use when designing data-heavy components, handling API calls, building hero sections, or improving…
motion-and-storytelling
Disney's 12 animation principles, cinematic storytelling techniques, and comic book conventions apply to web UI — used subtly, they make interfaces feel alive, intentional, and emotionally resonant. Use when designing transitions, micro-interactions, onboarding flows, scroll animations, or any motion in the UI.
performance-and-web-vitals
Audit UI performance with Lighthouse and fix Core Web Vitals — LCP, CLS, INP. Fast UI is good UX. Use when optimising page load, fixing layout shift, reducing input delay, improving Lighthouse scores, or reviewing images, fonts, and render-blocking resources.