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 agentmods add skills/sso-ss/vibe-ship-it/web-nextjsnpx skills add sso-ss/vibe-ship-it --skill web-nextjsgit clone --depth 1 https://github.com/sso-ss/vibe-ship-itWhat 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 | $0.00026 | $0.01223 |
| Opus 5 | $0.00013 | $0.00611 |
| Sonnet 5 | $0.00005 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
web-nextjs 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 yesterday.
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.
Web Platform: Next.js
The default web stack. Next.js App Router + Tailwind CSS + Supabase + Vercel.
Project Structure
Explain to the designer as:
"Your project is organized into folders. Think of each folder as a room with a specific purpose."
src/
app/ ← Pages (each folder = a page on your site)
page.tsx ← Home page (yourdomain.com/)
layout.tsx ← The wrapper around every page (nav, footer)
about/
page.tsx ← About page (yourdomain.com/about)
contact/
page.tsx ← Contact page (yourdomain.com/contact)
dashboard/
page.tsx ← Dashboard (yourdomain.com/dashboard)
login/
page.tsx ← Login page (yourdomain.com/login)
actions.ts ← Server actions (code that saves data)
components/ ← Reusable pieces (navigation, footer, cards)
utils/
supabase/
server.ts ← Server-side database connection
client.ts ← Browser-side database connection
middleware.ts ← Page protection (bouncer for private pages)
public/ ← Static files (images, favicon)
.env.local ← Secret settings (database keys, API keys)
Key Conventions
Server vs Client Components
Don't explain "server components" and "client components" in those terms. Say:
- Default (server): "This code runs on the server before the page is sent to the visitor. Good for loading data from the database."
'use client': "This code runs in the visitor's browser. Needed when things are interactive — forms, buttons that do stuff, anything that changes on screen."
Rule of thumb:
- Page shows data from database → server component (default, no directive)
- Page has interactive elements (forms, modals, toggles) → add
'use client'at the top
Server Actions
Explain as: "Code that runs when someone submits a form."
'use server'
export async function doSomething(formData: FormData) {
// This runs on the server, not in the visitor's browser
// Safe to access the database here
}
What ships with it
1 file 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.
- yesterday First seen · 161 lines · 26 tokens per session scan A 7694ca071d0f
web-nextjs is a skill published in the GitHub repository sso-ss/vibe-ship-it (10 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 1,223 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…