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/imsaif/design-with-claudeWrote 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/commands/imsaif/design-with-claude/deploy-to-vercel)<a href="https://agentmods.dev/commands/imsaif/design-with-claude/deploy-to-vercel"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/deploy-to-vercel/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/commands/imsaif/design-with-claude/deploy-to-vercel"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/deploy-to-vercel.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.00035 | $0.00724 |
| Opus 5 | $0.00017 | $0.00362 |
| Sonnet 5 | $0.00007 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
deploy-to-vercel 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 9d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Deployment Guide for designers. When invoked with $ARGUMENTS, you walk the designer through deploying their project to Vercel — getting it live on the internet — in plain language, step by step.
What is Vercel (designer explanation)
"Vercel is like a hosting service for your project. Right now your app only runs on your computer. Vercel puts it on the internet so anyone can access it. It's free for personal projects and takes about 5 minutes to set up."
Setup Sequence
Step 1 — Push your project to GitHub
If your project isn't on GitHub yet:
git init
git add .
git commit -m "Initial commit"
Then create a new repo at https://github.com/new and follow the instructions to push.
Step 2 — Create a Vercel account
Go to https://vercel.com and sign up with GitHub.
Step 3 — Import your project
- Click Add New → Project
- Select your GitHub repo
- Click Import
Step 4 — Add environment variables
Before clicking Deploy:
- Expand Environment Variables
- Add every variable from your
.env.localfile - This is critical — without these, your deployed app won't connect to Supabase, Clerk, or any other service
Step 5 — Deploy
Click Deploy. Vercel builds your project and gives you a live URL (something like yourproject.vercel.app).
Step 6 — Set up a custom domain (optional)
- Go to your project in Vercel → Settings → Domains
- Add your domain
- Update your domain's DNS settings as Vercel instructs (usually takes 10-30 minutes)
Fixing common build errors
"Module not found":
A package used in your code isn't installed. Run npm install locally, commit, and push again.
"Type error: X is not assignable to type Y": A TypeScript error. Share the exact error message and the file it points to — the fix is usually a small code change.
"Environment variable X is undefined": You forgot to add this variable in Vercel's Environment Variables settings. Go to Vercel → Project → Settings → Environment Variables and add it.
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.
- 9d ago First seen · 74 lines · 35 tokens per session scan A e61b14f65d4c
deploy-to-vercel is a command published in the GitHub repository imsaif/design-with-claude (11 stars, last pushed 19d ago), licensed MIT. It adds 35 tokens to every session and 724 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-30.
Other commands, from other repositories
audit
Run a full UI/UX design audit on the current project. Scores 12 dimensions and produces a markdown report with prioritized findings.
a11y
Run an accessibility-only audit — focus indicators, skip links, alt text, prefers-reduced-motion, WCAG contrast. Scoped variant of /ui-ux-suite:audit.
colors
Run a color-only design audit — contrast, near-duplicates, dark mode, semantic coverage. Scoped variant of /ui-ux-suite:audit.
components
Run a component-quality audit — state coverage, primitive consistency, cn()/CVA patterns. Scoped variant of /ui-ux-suite:audit.
typography
Run a typography-only audit — scale detection, font count, body size, line height, fluid type. Scoped variant of /ui-ux-suite:audit.
make-carousel
Design and produce a social media carousel (Instagram / LinkedIn / TikTok) — hook, narrative slides, CTA — with a consistent template and rendered slides.