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 jj-jamen/buildable-plugin-skills --skill web-buildergit clone --depth 1 https://github.com/jj-jamen/buildable-plugin-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/jj-jamen/buildable-plugin-skills/web-builder)<a href="https://agentmods.dev/skills/jj-jamen/buildable-plugin-skills/web-builder"><img src="https://agentmods.dev/badge/skills/jj-jamen/buildable-plugin-skills/web-builder.svg" alt="Measured on agentmods" 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.00035 | $0.00613 |
| Opus 5 | $0.00017 | $0.00307 |
| Sonnet 5 | $0.00007 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
buildable-web-builder 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 6d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Buildable Web Builder Skill
Use this skill to generate or adapt local web prototypes.
Resolve all referenced paths from the Buildable plugin or repository root.
Activation
Use only when the user is building or adapting a web app/prototype. Do not activate for unrelated frontend debugging unless the user asks for Buildable guidance.
Reference Loading Contract
Mandatory order:
- Read the saved planner output first:
.buildable/phase-plan.jsonwhen present, otherwisebuildable-app-spec.json. Use.buildable/phase-plan.toonwhen present as the compact agent-facing build contract. - Load only
appSpec.references. - Load current project files only as needed for the requested change.
- Do not load all templates.
- Load starter source only for the selected template and only when generating or editing it.
Default Stack
- Next.js
- TypeScript
- Tailwind CSS
- shadcn-style component patterns
- local/mock data
Workflow
- Read the saved plan/app spec from the planner handoff.
- Check
appSpec.planAudit.checksbefore editing; treat blocked/failed checks as gates, not suggestions. - If
questionsNeededis true, ask the user before generating. - For fresh starts, prefer
buildable generate "<prompt>"when a runnable template exists. Add--out <dir>only when the user requested a specific folder. - Apply
appSpec.designSystemfor visual tone, density, palette intent, layout rules, component rules, accessibility, and anti-patterns. - Apply
appSpec.blocksas reusable micro-template guidance. Selected block docs are references to adapt to the current entity/design system, not generic code to paste blindly. - If
appSpec.auth.requestedis true, implement the local/mock auth shape first and keep any named provider behind the auth seam. - Load only the references listed in the app spec.
- If the template is
generic-app, use the selected archetype reference to shape screens and entities instead of loading unrelated templates. - Inspect the local project if generating inside an existing app.
- Generate or adapt a complete first-screen prototype.
- Keep data local unless the spec explicitly requires otherwise.
- Run build/typecheck/lint checks when available.
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.
- 6d ago First seen · 63 lines · 35 tokens per session scan A bcc797195179
buildable-web-builder is a skill published in the GitHub repository jj-jamen/buildable-plugin-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 613 once invoked, about $0.0002 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…
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.
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.
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…
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…