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 rules/toyamarinyon/giselle/design-modegit clone --depth 1 https://github.com/toyamarinyon/giselleWrote 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/toyamarinyon/giselle/design-mode)<a href="https://agentmods.dev/rules/toyamarinyon/giselle/design-mode"><img src="https://agentmods.dev/badge/rules/toyamarinyon/giselle/design-mode.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.00017 | $0.01052 |
| Opus 5 | $0.00009 | $0.00526 |
| Sonnet 5 | $0.00003 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
design-mode 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 5d 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.
This is a copy
100% identical to design-mode — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Mode
Design Mode is intended for users who excel in design rather than software development. It enables direct application design by editing Next.js code instead of using tools like Figma.
- Avoid destructive changes.
- Limit modifications to appearance or behavior only.
- If functional changes or additions are necessary, create a consultation text for engineers and encourage the user to seek their input.
How to Start Design Mode
The step-by-step procedure below MUST be followed in order. Each step MUST be completed before proceeding to the next one. No steps should be skipped.
1. Check Requirements
All required tools must be verified in the following order:
-
Node.js Version Check
node -v✅ REQUIRED: Version must be 22.14.0 or later ❌ If version requirement not met: See
./nodejs.mdcfor installation instructions -
pnpm Version Check
pnpm -v✅ REQUIRED: Version must be 10.2.1 or later ❌ If version requirement not met: See
./nodejs.mdcfor installation instructions -
Vercel CLI Version Check
vercel --version✅ REQUIRED: Version must be 41.6.0 or later ❌ If Vercel CLI is missing: Install with the command below
pnpm add -g vercel -
Vercel CLI Login Status
vercel whoami✅ REQUIRED: Must show a username ❌ If not logged in: See
./vercel-cli.mdcfor login instructions -
Vercel Project Link Check
[ -f .vercel/project.json ] && echo "Project is linked" || echo "We need to link vercel project"✅ REQUIRED: Must show "Project is linked" ❌ If "We need to link vercel project" is displayed: a. List available teams:
bash vercel team listb. Switch to team and list projects:bash vercel team switch [team-name] vercel project listc. Link the project:bash vercel link --yes --project [project-name]
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.
- 5d ago First seen · 150 lines · 17 tokens per session scan A 5f9bf41b449c
design-mode is a cursor rule published in the GitHub repository toyamarinyon/giselle (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,052 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to design-mode, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
shadcn-tailwind-guide
本规范定义了使用 shadcn/ui 和 Tailwind CSS 开发新组件的标准流程和最佳实践。.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.