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 what-am-i-buildinggit 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/what-am-i-building)<a href="https://agentmods.dev/skills/sso-ss/vibe-ship-it/what-am-i-building"><img src="https://agentmods.dev/badge/skills/sso-ss/vibe-ship-it/what-am-i-building/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/what-am-i-building"><img src="https://agentmods.dev/badge/skills/sso-ss/vibe-ship-it/what-am-i-building.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.00062 | $0.01451 |
| Opus 5 | $0.00031 | $0.00726 |
| Sonnet 5 | $0.00012 | $0.00290 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
what-am-i-building 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What Am I Building
The entry point for every new project. Translates the designer's idea into a working scaffold as fast as possible.
Fast Mode (Default)
Ask ONE question, then scaffold. Do not front-load planning.
The Question
"What are you making? Give me the quick version — what does someone DO when they visit?"
From Their Answer, Extract
- Platform — web, mobile, desktop, or other (see routing table below)
- Core action — the ONE thing a visitor does (book, buy, read, contact, upload)
- First visible thing — the landing page / first screen
Then Immediately
- Show a simple flow map:
📍 Here's how it'll work: [Visitor arrives] → [Sees X] → [Does Y] → [Result Z] - Scaffold the project
- Start the dev server
- Show the first page in the browser
Total time from idea to first page in browser: under 5 minutes.
Platform Routing
Supported
| They say | Platform | Stack |
|---|---|---|
| "website", "landing page", "portfolio", "blog" | Web | Next.js + Tailwind + Supabase + Vercel |
| "web app", "dashboard", "tool", "SaaS" | Web | Next.js + Tailwind + Supabase + Vercel |
| "app", "iPhone", "Android", "mobile" | Mobile | React Native + Expo + Supabase + EAS |
| "Figma plugin", "extend Figma" | Figma Plugin | TypeScript + Figma Plugin API |
Not Yet Supported — Offer Alternatives
| They say | What to do |
|---|---|
| "store", "sell", "shop", "products" | Offer a web app with a products page and Stripe checkout |
| "blog", "CMS", "content site" | Offer Next.js with markdown files or Supabase as a simple CMS |
| "email template", "newsletter" | Offer to build the email with HTML + Resend |
| "desktop app", "Mac app" | Not supported. Suggest building as a web app instead |
| "art", "generative", "creative" | Not supported. Suggest a web-based canvas with p5.js if simple |
If the designer asks for something not supported, don't pretend. Say: "I'm set up for websites, mobile apps, and Figma plugins right now. Want me to build it as a [closest supported option]?"
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.
- 12d ago First seen · 175 lines · 62 tokens per session scan A ba31b1695d30
what-am-i-building is a skill published in the GitHub repository sso-ss/vibe-ship-it (12 stars, last pushed 5mo ago), licensed MIT. It adds 62 tokens to every session and 1,451 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…