buildable-design

buildable-design is a command for Claude Code, Cursor from suntay44/buildable-plugin-skills. It costs 0 tokens per session (260 once invoked), scanned A, original, MIT.

A command that creates a user-interface and user-experience brief from a prompt or an existing Buildable app specification. It covers the requested screen or app design, including light or dark visual direction.

In plain words
What is it for?
Use it to plan pages such as login screens, define visual rules, and prepare a design brief for a later build step.
Why use it?
It separates design decisions from implementation, so the intended screens and interaction style are clear before development begins.

Command for Claude CodeCursor

Written for Claude Code and Cursor: shipped in a Claude Code plugin, but also installed under .cursor/.

Part of the buildable plugin — 4 skills, 7 commands, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add commands/suntay44/buildable-plugin-skills/buildable-design
Clone the repo
git clone --depth 1 https://github.com/suntay44/buildable-plugin-skills

Made for: Claude Code, Cursor.

Or install buildable, the plugin that ships this one along with the rest of its 4 skills, 7 commands, 1 MCP server.

Wrote 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.

agentmods badge for buildable-design

README.md
[![agentmods](https://agentmods.dev/badge/commands/suntay44/buildable-plugin-skills/buildable-design.svg)](https://agentmods.dev/commands/suntay44/buildable-plugin-skills/buildable-design)
Your own site
<a href="https://agentmods.dev/commands/suntay44/buildable-plugin-skills/buildable-design"><img src="https://agentmods.dev/badge/commands/suntay44/buildable-plugin-skills/buildable-design.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 260 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00260
Opus 5 $0.00000 $0.00130
Sonnet 5 $0.00000 $0.00052
Haiku 4.5 $0.00000 $0.00026

Measured 6d ago against content hash 78a410ab88e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

buildable-design 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.cursor/commands/buildable-design.md · 16 lines

What it actually says

Buildable Design

Create a UI/UX design brief from a prompt or the current Buildable app spec.

Run:

buildable design "<prompt>" 2>/dev/null || node "${BUILDABLE_ROOT:?Set BUILDABLE_ROOT to your Buildable checkout}/bin/buildable.mjs" design "<prompt>"

Use --page "login" or similar for a specific surface. Add --dark (or say "dark mode" in the prompt) to make the dark palette the active theme. Add --write only when the user wants .buildable/design-brief.json and .buildable/design-brief.md saved into the workspace.

If buildable-app-spec.json exists, keep that app context. Otherwise, let design classify the prompt. Load only the references listed in the design brief and apply the tokens/rules to the requested app, page, or component.

buildable design is UI/UX-only. Do not add backend code, databases, auth, payments, hosted infrastructure, telemetry, or deployment from this command. End by asking whether the user is satisfied with the UI/UX direction and mockup-data plan. If yes, offer the brief's nextSuggestedCommand as the build phase.

Changes

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.

  1. 6d ago First seen · 16 lines · 0 tokens per session scan A 78a410ab88e8

Subscribe to this mod's changes

buildable-design is a command published in the GitHub repository suntay44/buildable-plugin-skills (53 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 260 tokens. 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-30.