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.
git clone --depth 1 https://github.com/bmoff/code-first-designWrote 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/rules/bmoff/code-first-design/code-first-design-create)<a href="https://agentmods.dev/rules/bmoff/code-first-design/code-first-design-create"><img src="https://agentmods.dev/badge/rules/bmoff/code-first-design/code-first-design-create/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/rules/bmoff/code-first-design/code-first-design-create"><img src="https://agentmods.dev/badge/rules/bmoff/code-first-design/code-first-design-create.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.00013 | $0.02015 |
| Opus 5.5 | $0.00005 | $0.00806 |
| Sonnet 5.5 | $0.00003 | $0.00403 |
| Haiku 4.5 | $0.00001 | $0.00201 |
Grade A, and why
code-first-design-create 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 1mo 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating draft components and prototypes
Before you start: Read code-first-design.mdc to understand how the framework works, especially the "How it works" and "Components vs prototypes" sections. This rule helps you create either a component (individual UI piece) or a prototype (full application flow).
⚠️ IMPORTANT: You MUST ask planning questions BEFORE starting implementation. Do not jump straight to code. Clarify what the user wants first, then proceed.
Planning questions (ask these first)
Before creating anything, ask these questions to understand what the user wants:
-
What are you creating?
- Is it a component (like a button, card, or form - a single reusable piece)?
- Or is it a prototype (a complete page or flow that shows multiple components working together)?
-
What should it do?
- What's its purpose? What problem does it solve?
- What should users be able to do with it?
- What information does it need? (For components: what information does the component need to work? For prototypes: what pages or screens does it need?)
-
What should it look like?
- Any specific design requirements?
- Should it match existing components or have a new style?
- Any accessibility needs to consider?
-
How should it behave?
- Does it need to respond to user clicks or input? (If yes, it needs to be interactive)
- Or is it just displaying information? (If yes, it can be simpler)
-
If creating a prototype, also ask:
- What pages or screens does it need?
- What components will it use? Are they new or do they already exist?
- How should users navigate through it?
Workflow:
- If the user's request is vague, ask these questions explicitly
- If the user provides detailed information and you're confident about the answers, summarise your understanding and any assumptions you're making (keep it clear and concise)
- Only proceed to implementation steps once you have confirmed understanding
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.
- 1mo ago First seen · 199 lines · 13 tokens per session scan A adc04eb73061
code-first-design-create is a cursor rule published in the GitHub repository bmoff/code-first-design (4 stars, last pushed 11mo ago), licensed MIT. It adds 13 tokens to every session and 2,015 once invoked, about $0.0001 per session on Opus 5.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 cursor rules, from other repositories
external-scale
Source: docs/agents/external-scale.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
mobile-first-ui
Mobile-first UI for settings, dialogs, and lists — smaller type, stacked layouts, nested add dialogs.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.
frontend-design-direction
Derive a brief-specific visual direction, token sketch, hierarchy, and signature element.