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 sso-ss/vibe-ship-it --skill build-pagegit clone --depth 1 https://github.com/sso-ss/vibe-ship-itWrote 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/sso-ss/vibe-ship-it/build-page)<a href="https://agentmods.dev/skills/sso-ss/vibe-ship-it/build-page"><img src="https://agentmods.dev/badge/skills/sso-ss/vibe-ship-it/build-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/sso-ss/vibe-ship-it/build-page"><img src="https://agentmods.dev/badge/skills/sso-ss/vibe-ship-it/build-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.00108 | $0.01641 |
| Opus 5 | $0.00054 | $0.00821 |
| Sonnet 5 | $0.00022 | $0.00328 |
| Haiku 4.5 | $0.00011 | $0.00164 |
Grade A, and why
build-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 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Page
Turns descriptions, screenshots, or Figma designs into working UI. The designer's primary creative tool.
Input Types
1. Text Description
"I want a landing page with a big headline, some portfolio images in a grid, and a contact form at the bottom"
→ Decompose into sections, generate each, preview immediately.
2. Screenshot / Image
pastes or uploads an image
→ Analyze the layout, colors, typography, and spacing. Reproduce as closely as possible. Ask: "Does this match? What should change?"
3. Figma Reference
"Here's my Figma design" / provides a Figma link
→ If Figma MCP is available, pull design data directly. Otherwise, ask them to screenshot the specific frame.
4. Vague Request
"make me a website"
→ Don't ask 10 questions. Pick a sensible default (clean landing page with hero, features section, CTA), build it, show it. They'll tell you what to change.
Build Process
Step 1: Decompose
Break the page into sections mentally. Don't show the decomposition to the designer — just build.
Typical page anatomy:
- Navigation (header)
- Hero section (headline + CTA)
- Content sections (features, portfolio, testimonials, etc.)
- Forms (contact, signup, booking)
- Footer
Step 2: Generate
Build the full page in one go. Use:
- Tailwind CSS for all styling
- Semantic HTML
- Good defaults: comfortable spacing, readable typography, balanced proportions
- Real-looking placeholder content (not "Lorem ipsum" — use realistic copy)
Step 3: Preview
Ensure dev server is running. Tell the designer:
"Check your browser — here's what it looks like."
Step 4: Iterate
Wait for feedback. Common responses and what to do:
| They say | They mean | Do |
|---|---|---|
| "Perfect!" | Done | Move on |
| "Close but..." | Needs tweaks | Ask what specifically |
| "The spacing feels off" | Padding/margin/gap issue | Adjust spacing, show again |
| "Too much text" | Content is overwhelming | Reduce copy, increase white space |
| "Make it more [adjective]" | Aesthetic change | Apply the vibe (see adjective table below) |
| "Like [reference site]" | Match an external reference | Analyze the reference, adapt to their content |
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 · 161 lines · 108 tokens per session scan A 5d01f692363c
build-page is a skill published in the GitHub repository sso-ss/vibe-ship-it (12 stars, last pushed 5mo ago), licensed MIT. It adds 108 tokens to every session and 1,641 once invoked, about $0.0005 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.